▲ 332 ▼ GitLab Act 2 - A letter to our customers and our investors. (about.gitlab.com) submitted 4 months ago by tofu@lemmy.nocturnal.garden to c/selfhosted@lemmy.world 139 comments fedilink hide all child comments Lots of layoffs ("re-evaluating our operational footprint") and switching to "agentic" processes. Target user is AI. Anyone still hosting Gitlab?
[–] tofu@lemmy.nocturnal.garden [S] 122 points 4 months ago (6 children) If you don't want to host something yourself, check codeberg permalink fedilink source parent hideshow 6 child comments replies: [–] pluge@piefed.social 15 points 4 months ago (5 children) I like codeberg and have no plans on migrating away from it, but their codeberg Pages product is...weak to say the least. There's very frequent downtime. I had multiple users reach out to me letting me know my site was down... embarrassing. I set up kuma uptime checks on it, and now I see when the outages happen. Forget "four 9's" or anything close to that....my 30 day uptime is a measley 91%... permalink fedilink source parent hideshow 5 child comments replies: [–] sonstwas@sh.itjust.works 21 points 4 months ago* (last edited 4 months ago) (1 child) They communicate that openly tho: Regular maintenance window: We're meeting every Tuesday starting 18.00 Berlin time (currently 17.00 UTC), lasting up to 8 hours. While we announce large scheduled downtimes in advance, there might be minor interruptions due to maintenance work happening during the meeting. Please be patient in this case. https://status.codeberg.org/status/codeberg Not sure if that's also for the Pages feature, but in general having a weekly 8hr maintenance window is not optimal. permalink fedilink source parent hideshow 1 child comment replies: [–] pluge@piefed.social 4 points 4 months ago That's true, but even at worst case (full 8 hour outage per week) that's still 96% uptime. Most of my outages have been out of that window. permalink fedilink source parent [–] ell1e@leminal.space 4 points 4 months ago (1 child) Github seems to be down a lot, too, although perhaps not their pages part. Perhaps you could try to have just the pages in some other place? permalink fedilink source parent hideshow 1 child comment replies: [–] pluge@piefed.social 2 points 4 months ago That's true! I've read recently that GitHub's uptime is pretty terrible too. My site is low enough stakes that I can live with it on codeberg. I just relaxed the uptime check a bit so it only alarms if I have an extended outage. Even so, the alarms aren't actionable to me...other than maybe announcing to my users that there's an outage rather than having them ask me if I'm aware of the outage. permalink fedilink source parent [–] vogi@piefed.social 2 points 4 months ago Thats rough. Check out https://grebedoc.dev/ I believe codeberg itself also wants to migrate to that as well, I cant tell you how reliable it is though (I am using hetzner managed for 1.90€/m) is but I dig its simplicity. permalink fedilink source parent
[–] pluge@piefed.social 15 points 4 months ago (5 children) I like codeberg and have no plans on migrating away from it, but their codeberg Pages product is...weak to say the least. There's very frequent downtime. I had multiple users reach out to me letting me know my site was down... embarrassing. I set up kuma uptime checks on it, and now I see when the outages happen. Forget "four 9's" or anything close to that....my 30 day uptime is a measley 91%... permalink fedilink source parent hideshow 5 child comments replies: [–] sonstwas@sh.itjust.works 21 points 4 months ago* (last edited 4 months ago) (1 child) They communicate that openly tho: Regular maintenance window: We're meeting every Tuesday starting 18.00 Berlin time (currently 17.00 UTC), lasting up to 8 hours. While we announce large scheduled downtimes in advance, there might be minor interruptions due to maintenance work happening during the meeting. Please be patient in this case. https://status.codeberg.org/status/codeberg Not sure if that's also for the Pages feature, but in general having a weekly 8hr maintenance window is not optimal. permalink fedilink source parent hideshow 1 child comment replies: [–] pluge@piefed.social 4 points 4 months ago That's true, but even at worst case (full 8 hour outage per week) that's still 96% uptime. Most of my outages have been out of that window. permalink fedilink source parent [–] ell1e@leminal.space 4 points 4 months ago (1 child) Github seems to be down a lot, too, although perhaps not their pages part. Perhaps you could try to have just the pages in some other place? permalink fedilink source parent hideshow 1 child comment replies: [–] pluge@piefed.social 2 points 4 months ago That's true! I've read recently that GitHub's uptime is pretty terrible too. My site is low enough stakes that I can live with it on codeberg. I just relaxed the uptime check a bit so it only alarms if I have an extended outage. Even so, the alarms aren't actionable to me...other than maybe announcing to my users that there's an outage rather than having them ask me if I'm aware of the outage. permalink fedilink source parent [–] vogi@piefed.social 2 points 4 months ago Thats rough. Check out https://grebedoc.dev/ I believe codeberg itself also wants to migrate to that as well, I cant tell you how reliable it is though (I am using hetzner managed for 1.90€/m) is but I dig its simplicity. permalink fedilink source parent
[–] sonstwas@sh.itjust.works 21 points 4 months ago* (last edited 4 months ago) (1 child) They communicate that openly tho: Regular maintenance window: We're meeting every Tuesday starting 18.00 Berlin time (currently 17.00 UTC), lasting up to 8 hours. While we announce large scheduled downtimes in advance, there might be minor interruptions due to maintenance work happening during the meeting. Please be patient in this case. https://status.codeberg.org/status/codeberg Not sure if that's also for the Pages feature, but in general having a weekly 8hr maintenance window is not optimal. permalink fedilink source parent hideshow 1 child comment replies: [–] pluge@piefed.social 4 points 4 months ago That's true, but even at worst case (full 8 hour outage per week) that's still 96% uptime. Most of my outages have been out of that window. permalink fedilink source parent
[–] pluge@piefed.social 4 points 4 months ago That's true, but even at worst case (full 8 hour outage per week) that's still 96% uptime. Most of my outages have been out of that window. permalink fedilink source parent
[–] ell1e@leminal.space 4 points 4 months ago (1 child) Github seems to be down a lot, too, although perhaps not their pages part. Perhaps you could try to have just the pages in some other place? permalink fedilink source parent hideshow 1 child comment replies: [–] pluge@piefed.social 2 points 4 months ago That's true! I've read recently that GitHub's uptime is pretty terrible too. My site is low enough stakes that I can live with it on codeberg. I just relaxed the uptime check a bit so it only alarms if I have an extended outage. Even so, the alarms aren't actionable to me...other than maybe announcing to my users that there's an outage rather than having them ask me if I'm aware of the outage. permalink fedilink source parent
[–] pluge@piefed.social 2 points 4 months ago That's true! I've read recently that GitHub's uptime is pretty terrible too. My site is low enough stakes that I can live with it on codeberg. I just relaxed the uptime check a bit so it only alarms if I have an extended outage. Even so, the alarms aren't actionable to me...other than maybe announcing to my users that there's an outage rather than having them ask me if I'm aware of the outage. permalink fedilink source parent
[–] vogi@piefed.social 2 points 4 months ago Thats rough. Check out https://grebedoc.dev/ I believe codeberg itself also wants to migrate to that as well, I cant tell you how reliable it is though (I am using hetzner managed for 1.90€/m) is but I dig its simplicity. permalink fedilink source parent