you: installing mastodon is hard
gitlab: hold my beer
@CobaltVelvet I want to be in control of the postgres/redis that it uses. Omnibus installs its own nginx too. It's basically sacrificing the entire machine to GitLab.
@gargron i remember the omnibus config to be very powerful https://stackoverflow.com/questions/29949294/how-to-configure-gitlab-to-use-existing-postgres-server
but tbh i'd recommend keeping gitlab self-contained, and maybe splitting that machine using lxc or xen/kvm
@gargron @CobaltVelvet but you don't need to use the bundled stuff it comes with, here the postgres example!
@gargron @kurisu and the absolute conclusion would be, give a standard box to the installer and the installer will make it work, and you can start over and load backups in another standard box with the same installer if needed
even if sometimes it doesn't look like it that's peak performance on a human scale
and by box i mean a lxc container would be great at that and not add much overhead, and then you can just manage those clean isolated boxes on your server and run apt upgrade every time a gitlab release looks cool. i've been using omnibus for months and it has been flawlessly simple and efficient for my time, even for upgrades or backups
@Gargron heh fair. I've had a lot of negative experiences with docker but it's still the way to go to get stuff up and running IMO
@j No, I've always known about that from the documentation. My instance used to be hosted via Docker and all of the failures were from Docker acting up in weird and unpredictable ways.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!