|
We have a patch for gitlab in nixos that fixes a lot of our problems. I don't know why we never tried to upstream it, but I guess it's just that nobody bothered. I'll try cleaning it up and upstreaming it when I have some time. For the omnibus, I'll try looking at how it works, see if it fits our needs better. But I suppose gitaly, which is written in go, still has its own configuration elsewhere, in which you have to replicate the storage list ? That's the sort of thing that I find sort of annoying. It's not a huge issue, but having to manage a bunch of configs, making sure they're all synchronized and up to date sucks as a user experience. I do have to say, your upgrade guides are very nice and have been helpful when upgrading our instance :). As far as docker and other things go, I considered it while fighting to get gitlab 9 to work on bare nixos. But the thing is, I manage all my services through nixos, having a central place for all my configuration. This[0] is my configuration (well, a very old one). Everything is in one place, and everything can cross-reference each-other. See my firewall for instance[1], that cross-references various other service's configuration to get their port. With docker, this is much harder to achieve. [0]: https://gist.github.com/roblabla/8d1555ceb202eddb1b77 [1]: https://gist.github.com/roblabla/8d1555ceb202eddb1b77#file-c... |
So yes, Gitaly does come with it's own configuration file that needs to be managed. It does use the same paths as the main gitlab-rails application, so our cookbook has a method to convert the configuration of one to the other[1]
[0]: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/fil...
[1]: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/fil...