We are running omnibus GitLab on a local server. We have to tweak some internals of it; partly these changes are due to reported bugs not integrated yet, partly requested features that will be added probably never and implemented as very simple hacks, and partly those very specific to out environment and of little interest to community.
I am sure we are not alone in this boat. What is the best practice for managing patches for the omnibus package? Currently I have a Git repository at /opt/gitlab/embedded/service/gitlab-rails on the production server, and am keeping two branches, "vendor" and "local". A new version brought in by "apt-get" is checked into the vendor branch, and then I rebase the local head on top of the new master tag. Sounds stable but one must remember a lot of things (checkout the vendor branch before apt-get upgrade is one of them). So this is not the best possible solution, and another admin can unknowingly create a big mess there. So how other people maintain their local patches? -kkm -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/ec9776be-f175-4f3b-9089-4dae3360d2d9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
