6 ms·

I migrated my entire workflow onto a personal GitLab instance after the whole "pay a fee to bring your own bags to the grocery store" GitHub Actions pricing she

I migrated my entire workflow onto a personal GitLab instance after the whole "pay a fee to bring your own bags to the grocery store" GitHub Actions pricing shenanigans earlier this year. Best decision ever. 100% uptime. 100% less stress with each of the product/pricing changes over the past few months. Was also able to build my own GitHub Copilot equivalent that auto-reviews MRs interactively. Highly recommend it.

colechristensen 5mo ago
Is GitLab pretty good these days? I remember quite a few years ago it having its own set of problems.
- shimman 5mo ago
  Yeah, if you're hosting your own just use forgejo. Forgejo has a better governance model and is actually open source, not a corporate project that happens to advertise in open source. The distinction is meaningful.
  - mixmastamyk 5mo ago
    Also written in golang so much faster using fewer resources.
  - bsza 5mo ago
    It's also probably easier to migrate to if you have complex workflows as Forgejo Actions is designed to be similar to GH Actions. (Never actually tried it myself though, I switched to Woodpecker long ago.)
- cyberpunk 5mo ago
  forgejo has been great for us. It scales remarkably far with the built in sqlite db also. Single binary, no deps. You ofc have the option to hook it up to a proper database server.
- whalesalad 5mo ago
  It’s a rails app from the early 10’s era think heroku dominance. therefore to run it you’ll need a dozen sidecars for things like redis or elasticsearch and others. it has all the fun ergonomics and bloated memory consumption of that stack as well. the all-in-one go based tools are probably better for a solo homelab style deployment (gitea etc)
  - colechristensen 5mo ago
    Eh, it wasn't about the stack, it was the features over quality track they were taking for a few years there where what features they had were impressive (they really motivated GitHub to get off its butt and do some things) but there were plenty of experience and reliability problems.
    - whalesalad 5mo ago
      I just mean running it yourself comes with that heavy stack caveat. As far as a platform goes, it's a pretty comprehensive system.
- featherless 5mo ago
  I had steered away for a long while thinking it was subpar to GitHub, but it's really come a long way. Especially running it on a local network it's noticeably faster in every way than GitHub, and I'm able to build complex gitlab workflows with custom runners that are fully configurable and have effectively 100% uptime and no queues.
faangguyindia 5mo ago
i am opposed to using anything which is not single binary and not using a sqlite db for self hosted things which don't need to scale to millions of users.

colechristensen 5mo ago

Is GitLab pretty good these days? I remember quite a few years ago it having its own set of problems.

shimman 5mo ago
Yeah, if you're hosting your own just use forgejo. Forgejo has a better governance model and is actually open source, not a corporate project that happens to advertise in open source. The distinction is meaningful.
- mixmastamyk 5mo ago
  Also written in golang so much faster using fewer resources.
- bsza 5mo ago
  It's also probably easier to migrate to if you have complex workflows as Forgejo Actions is designed to be similar to GH Actions. (Never actually tried it myself though, I switched to Woodpecker long ago.)
cyberpunk 5mo ago
forgejo has been great for us. It scales remarkably far with the built in sqlite db also. Single binary, no deps. You ofc have the option to hook it up to a proper database server.
whalesalad 5mo ago
It’s a rails app from the early 10’s era think heroku dominance. therefore to run it you’ll need a dozen sidecars for things like redis or elasticsearch and others. it has all the fun ergonomics and bloated memory consumption of that stack as well. the all-in-one go based tools are probably better for a solo homelab style deployment (gitea etc)
- colechristensen 5mo ago
  Eh, it wasn't about the stack, it was the features over quality track they were taking for a few years there where what features they had were impressive (they really motivated GitHub to get off its butt and do some things) but there were plenty of experience and reliability problems.
  - whalesalad 5mo ago
    I just mean running it yourself comes with that heavy stack caveat. As far as a platform goes, it's a pretty comprehensive system.
featherless 5mo ago
I had steered away for a long while thinking it was subpar to GitHub, but it's really come a long way. Especially running it on a local network it's noticeably faster in every way than GitHub, and I'm able to build complex gitlab workflows with custom runners that are fully configurable and have effectively 100% uptime and no queues.

faangguyindia 5mo ago

i am opposed to using anything which is not single binary and not using a sqlite db for self hosted things which don't need to scale to millions of users.