Below you will find some more info as well as the url of the testing environment. You can use/test it and report any issues here. If anyone needs an admin account for further testing just let me know. Just bare in mind that you might see some 500 errors as I will be trying some things.
More or less, here is the workflow I followed:
- Set up GitLab in a VM following the official installation guide and test everything works
rm -rf /vendor/bundle
- Test with
bundle install --local RAILS_ENV=production
- See the dependency differences
- Install with
yumthe gems in Gemfile
- Replace in Gemfile/Gemfile.lock with Fedora versions
- Repeat steps 3,4,5,6
There are a lot to be done yet until this reaches to the official repos but that's a start.
- Write the gitlab.spec that will glue all the dependencies together
- Commit as many specs as possible to BZ.
- GitLab forks: one option is to patch upstream with GitLab's changes. Second but rather avoided is to to ask FPC for an exception and package the forks as they are.
- Coordinate efforts with Debian ruby team (related discussion)
- Deploy on rawhide: when GitLab supports rails 4. That depends on many dependencies gems as well.
- port to EPEL