4 ms·

Gitlab users: How many hours per year do you spend on doing maintenance for your setup? (servers, updating, backups, troubleshooting, etc.)

chewmieser 10y ago
I login to my server once a week and run a yum update. Backups are scheduled, so I don't have to concern myself with that. No troubleshooting. But we're a small (<10 developers across 4 repos with access granted to ~ 30 people to GitLab for ticketing) team. Even my non-technical people are able to use GitLab for ticketing without bugging me, so that's fantastic. Love it.
icebraining 10y ago
Spent 30m installing it and configuring SSL. Nowadays I spend a couple of minutes monthly doing "aptitude update && aptitude install gitlab-ce" (after 5-15m reading about the new release, to see if it's worth it / problem free). We never had an issue with the auto-upgrade. It comes with support for automatic offsite backups (we use S3), so besides occasionally restoring to make sure they're working, that takes no time at all.
timmipetit 10y ago
0 hours, we pay for the hosted option via https://githost.io/ https://githost.io/
pluma 10y ago
I'm using paid GitLab hosting via the GitLab-owned GitHost.io, so zero: everytime an update comes out I get two e-mails and that's it. The pricing is extremely competitive. We are a small shop so the smallest package ($35, recommended for up to 30 active users) is good enough. We started with a self-hosted GitLab via docker and switched to GitHost as soon as it was bought by GitLab.
zegerjan 10y ago
If you don't want to maintain GitLab, either CE or EE, but would like to use it, you might want to take a look at GitHost.io The instance I maintain takes me about 15 minutes a month. Security updates are done automatically so all I've got left to do it 'apt-get install gitlab-ce' once or twice a month and thats it!
OliverJones 10y ago
Originally rigging gitlab-ce took a couple of hours, including standing up a VM, and setting up an S3 bucket for fire storage. Checking backups once a week, 3 min. Updates twice a month (using apt-get upgrade) 10 min counting integrity checks. Nuisance factor: updating gitlab-ce drops a tiny little backup file in the backups folder.
- jobvandervoort 10y ago
  If you want to skip the mini backup before upgrades, run: `sudo touch /etc/gitlab/skip-auto-migrations` Docs on it here: http://docs.gitlab.com/omnibus/update/README.html http://docs.gitlab.com/omnibus/update/README.html
chikei 10y ago
Like 5 min install it, ~30 min configure it, then about every two weeks spend 5~10 min check any new release and release notes, then just "docker-compose pull && docker-compose up -d" to upgrade.

chewmieser 10y ago

I login to my server once a week and run a yum update. Backups are scheduled, so I don't have to concern myself with that. No troubleshooting. But we're a small (<10 developers across 4 repos with access granted to ~ 30 people to GitLab for ticketing) team. Even my non-technical people are able to use GitLab for ticketing without bugging me, so that's fantastic. Love it.

icebraining 10y ago

Spent 30m installing it and configuring SSL. Nowadays I spend a couple of minutes monthly doing "aptitude update && aptitude install gitlab-ce" (after 5-15m reading about the new release, to see if it's worth it / problem free). We never had an issue with the auto-upgrade. It comes with support for automatic offsite backups (we use S3), so besides occasionally restoring to make sure they're working, that takes no time at all.

timmipetit 10y ago

0 hours, we pay for the hosted option via https://githost.io/ https://githost.io/

pluma 10y ago

I'm using paid GitLab hosting via the GitLab-owned GitHost.io, so zero: everytime an update comes out I get two e-mails and that's it. The pricing is extremely competitive. We are a small shop so the smallest package ($35, recommended for up to 30 active users) is good enough. We started with a self-hosted GitLab via docker and switched to GitHost as soon as it was bought by GitLab.

zegerjan 10y ago

If you don't want to maintain GitLab, either CE or EE, but would like to use it, you might want to take a look at GitHost.io The instance I maintain takes me about 15 minutes a month. Security updates are done automatically so all I've got left to do it 'apt-get install gitlab-ce' once or twice a month and thats it!

OliverJones 10y ago

Originally rigging gitlab-ce took a couple of hours, including standing up a VM, and setting up an S3 bucket for fire storage. Checking backups once a week, 3 min. Updates twice a month (using apt-get upgrade) 10 min counting integrity checks. Nuisance factor: updating gitlab-ce drops a tiny little backup file in the backups folder.

jobvandervoort 10y ago
If you want to skip the mini backup before upgrades, run: `sudo touch /etc/gitlab/skip-auto-migrations` Docs on it here: http://docs.gitlab.com/omnibus/update/README.html http://docs.gitlab.com/omnibus/update/README.html

chikei 10y ago

Like 5 min install it, ~30 min configure it, then about every two weeks spend 5~10 min check any new release and release notes, then just "docker-compose pull && docker-compose up -d" to upgrade.