kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss

Fork 0

Commit graph

Author	SHA1	Message	Date
Jan Provaznik	0fc9f9d3e7	Add version 4.2 to all existing migrations DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912	2018-11-22 13:18:28 +01:00
Alexis Reigel	703b39d440	truncate gpg signature instead of destroy	2017-09-05 12:18:34 +02:00
Alexis Reigel	aa98c36e47	destroy signatures instead of updating them This is faster for the deployment process, as the destroyed signatures will be re-generated on demand again, instead of updating them all on deploy.	2017-09-05 12:18:33 +02:00

Author

SHA1

Message

Date

Jan Provaznik

0fc9f9d3e7

Add version 4.2 to all existing migrations

DB schema generated by a migration may look different in
rails 4 and 5 (because rails 5 may use different default values).
For this reason it's important to explicitly set for which rails
version a migration was written for.

See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912

2018-11-22 13:18:28 +01:00

Alexis Reigel

703b39d440

truncate gpg signature instead of destroy

2017-09-05 12:18:34 +02:00

Alexis Reigel

aa98c36e47

destroy signatures instead of updating them

This is faster for the deployment process, as the destroyed signatures
will be re-generated on demand again, instead of updating them all on
deploy.

2017-09-05 12:18:33 +02:00

3 commits