mirror of
https://github.com/wahyd4/gitlabhq.git
synced 2026-08-13 14:46:05 +10:00
Robert SpeicherandRémy Coutable
3129e135eb
Reload the schema before restoring a database backup If a user tries to downgrade and restore after a failed upgrade, the database may still contain newer tables. Reload the older schema before restoring the database to avoid future upgrade problems. Also, add a rake task to help users add migration versions to the database so it's easier to recover from these errors if they do occur. Fixes #13419 See merge request !2807
1.5 KiB
1.5 KiB
Depending on the installation method and your GitLab version, there are multiple update guides. Choose one that fits your needs.
Omnibus Packages
- Omnibus update guide contains the steps needed to update a GitLab package.
Installation from source
- The individual upgrade guides are for those who have installed GitLab from source.
- The CE to EE update guides are for subscribers of the Enterprise Edition only. The steps are very similar to a version upgrade: stop the server, get the code, update config files for the new functionality, install libs and do migrations, update the init script, start the application and check the application status.
- Upgrader is an automatic ruby script that performs the update for installations from source.
- Patch versions guide includes the steps needed for a patch version, eg. 6.2.0 to 6.2.1.
Miscellaneous
- MySQL to PostgreSQL guides you through migrating your database from MySQL to PostgreSQL.
- MySQL installation guide contains additional information about configuring GitLab to work with a MySQL database.
- Restoring from backup after a failed upgrade