First of all welcome!
Since you are using postgres and the version is not that old, I’d say the upgrade path is fairly easy. The docs surely need an update.
I responded to a similar issue here. For your case I would follow these steps.
- Download omnibus 7.6.0 from the archives
- Install it on the new server and run
sudo gitlab-ctl reconfigure
at least once. - Backup the manual install.
- Transfer that backup file to
/var/opt/gitlab/backups
on the new server - On the new server run the restore process
- Edit
gitlab.rb
to matchgitlab.yml
- Run
gitlab-ctl reconfigure
and test that everything works - Take a backup with
sudo gitlab-rake gitlab:backup:create
just in case - Upgrade to latest version of omnibus first manually invoking dpkg or yum, then install the package server script so that the updates in the future are as easy as updating the server.
If the above works, then schedule a downtime window to properly take a backup with the db unmodified from new transactions. You can use the broadcast message feature (admin/broadcast_messages
) to notify the users.
As for the gitlab.yml
-> gitlab.rb
, there is a script in https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/support/gitlab_yml_converter.rb that does the heavy work. Just bare in mind that some settings might have been transfered to the admin area. For a full list of options see gitlab.rb.template
.
Good luck