We work on an internal gitlab instance that has had 100 percent up time for like 2 years. It doesn't even have to be gitlab, there's gitea and like 10 other options.

I personally think that the industry has moved so far in the direction of cloud and saas that it's lost a lot of valuable skills and made them dependent on too much externally.

[–] ripcord@lemmy.world 1 points 23 hours ago

Github has self-hosted options as well

[–] firelizzard@programming.dev 2 points 3 days ago (3 children)

I'm the only person at my (small startup) company who has the skills to maintain a GitLab instance. Been there, done that, never fucking again. I HATE maintenance. We're probably going to migrate to some other platform since GitHub is intent on turning to shit.

[–] Buckshot@programming.dev 2 points 3 days ago (1 children)

In 2014 I set up GitLab for my then employer. It had to be something self hosted because of client requirements. I was apparently the only one in a company of about 200 that knew anything about Linux.

Wasn't too bad, just keeping it up to date etc. When I left in 2016 I'd just upgraded the server to ubuntu 16.04. It's probably still running that now. I know someone who is still there and they've said GitLab itself hasn't been updated since I left.

[–] firelizzard@programming.dev 4 points 3 days ago

I set up and maintained a GitLab instance and GitLab CI runners for five years. It was fine. I still hated it. I loath maintaining infrastructure.

[–] tempest@lemmy.ca 1 points 3 days ago (1 children)

To each their own but ours didn't really require more than an hour a month at most. It's not running on cutting Edge hardware but chugs along pretty dependably. The back ups probably take the most time but even then ansible does most of the work and we bump the omnibus version once a month in off hours without issue.

[–] firelizzard@programming.dev 1 points 3 days ago

It’s not as much time as it is stress, anxiety, and trauma. Being on call when shit breaks is fucking awful and my best coping strategy to date is refusing to be an infrastructure person and aggressively not giving a fuck when things are down for a day or two.

[–] Magnum@infosec.pub -2 points 3 days ago (2 children)

Sounds like you don't really have the skill to maintain it.

[–] firelizzard@programming.dev 1 points 3 days ago

Oh fuck off. I’m not talking about the GitLab instance. Those aren’t hard. The trauma is from other stuff, but it adds a spicy flavor of stress and anxiety to all infrastructure work.

[–] Knock_Knock_Lemmy_In@lemmy.world 0 points 3 days ago (1 children)

24/7 maintenance is more a hassle issue than a skill issue.

[–] Magnum@infosec.pub 0 points 3 days ago (1 children)

There is something wrong with it, when it needs 24/7 maintenance.

[–] Knock_Knock_Lemmy_In@lemmy.world 1 points 3 days ago (1 children)

Not maintaining 24/7.

Responding to any incident within x minutes at any time of the day or night, everyday of the year.

[–] Magnum@infosec.pub 1 points 3 days ago (1 children)

This would be against the law in my country, especially if a single person is meant to fulfill that role 😂

[–] Knock_Knock_Lemmy_In@lemmy.world 1 points 3 days ago (1 children)

There's a big difference between working 24h and being on call in case of emergency 24h.

The latter is doable, just not very pleasant

[–] Magnum@infosec.pub 1 points 2 days ago* (last edited 2 days ago)

That is correct. But still you can't cover 24 hours in my country. It is what it is.

[–] Phoenix3875@lemmy.world 2 points 3 days ago* (last edited 3 days ago)

It's like "nobody ever got fired for buying IBM." Nobody ever got fired for pitching a migration to GitHub. It doesn't have to be good. Then one day it's crumbling down and people will have to learn to face consequences.