I understand that you have an installation from source, so, the usefulness of the following will depend on whether the database used by the source installation is the same as that used by the Omnibus installation. If they are the same, then this might help. My installation is also not concerned with web hooks or email.
I’ve just completed moving Omnibus Gitlab 6.5 using MySQL to Omnibus Gitlab 7.11.4 using Postgres on Ubuntu 14.04.
The strategy was roughly:
- Convert the MySQL database to Postgres using https://github.com/gitlabhq/mysql-postgresql-converter
- Do a fresh install of the latest Omnibus package on the destination server
- Import the legacy database into the new Omnibus instance*
- Copy legacy repositories into /var/opt/gitlab/git-data/repositories**
- Run the reconfiguration tool: sudo gitlab-ctl reconfigure
- Run the check tool: sudo gitlab-rake gitlab:check and fix any reported issues
- Run the database migrations: sudo gitlab-rake db:migrate RAILS_ENV=production
- Recreate satellites by running: sudo gitlab-rake gitlab:satellites:create
- Regenerate ssh keys by running: sudo gitlab-rake gitlab:shell:setup
- Run the reconfiguration tool (again): sudo gitlab-ctl reconfigure
- Restart Gitlab: sudo gitlab-ctl restart
*My system user for accessing the database is “gitlab-psql,” but my database, tables, and sequences are all owned by “gitlab”
**The repositories should be owned by the “git” user
The gist here is that if you have a good legacy database and a clean install of the latest Omnibus, you should be able to do it. The “gitlab-rake gitlab:check” command is your best friend here and can be run at just about any point during the upgrade. Omnibus also installs all the appropriate dependencies for you, so, no more time wrestling with ruby updates, etc.