4 ms·

I didn't know forgejo existed and I have been using gitlab ce which is getting more and more difficult to deal with for just home use. All of a sudden I see tha

I didn't know forgejo existed and I have been using gitlab ce which is getting more and more difficult to deal with for just home use. All of a sudden I see that I am no longer getting minor updates because my debian version isn't the latest and during my last update it broke the db again. forgejo seems to have everything I need including CI pipeline and container registry so I am definitely going to give it a try before trying to update gitlab.

omnimus 2y ago
It's also way easier than Gitlab to selfhost. Been running it for some time on small office NAS and it's solid.
jalict 2y ago
Switched from Gitlab to Forgejo at work and it is working fantastic for us. I am also using at home. Using both container registry and self-hosted runners, etc. I was personally very frustrated with ACL and generally inheritance rules in gitlab and it is much more sensible and easy in Forgejo.
dizhn 2y ago
FYI it's a fork of gitea, and like gitea, only a single go binary. Super easy to upgrade. I have been running gitea first and now forgejo under docker. It's literally a 5 minute deal to install once you know how it works.
- doubled112 2y ago
  I did a bare metal to Docker container migration in about 30 minutes a couple of weeks ago. It’s not a very complicated setup, with few surprises, and this system admin appreciates that.
mdaniel 2y ago
> including CI pipeline You'll want to be cautious, because readme and promises are not software; they're attempting to squat on[1] nektos/act[2] which itself is the 20/80 of GitHub Actions You'll almost certainly be happier using woodpecker[3] or some other "external" CI system so you don't have to hopes-and-prayers your CI system 1: https://code.forgejo.org/forgejo/act https://code.forgejo.org/forgejo/act 2: https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#L81 https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#... and https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#L286 https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#... 3: https://github.com/woodpecker-ci/woodpecker https://github.com/woodpecker-ci/woodpecker (Apache 2)
- egometry 2y ago
  what do you mean by "squat on"?
  - mdaniel 2y ago
    They didn't attempt to build a GitHub Action implementation, they took a known broken one and attempted to duct tape it, so now it's the worst of both worlds: maybe theirs is somehow better, but because everyone in the world knows how terrible act is, they have to say "oh, we built in top of act, but we added some things, fixed others, broke something else, and who knows[1] but good luck to you, our beta testers" Had act been a known working project, maybe it would have been worth the risk of forking it, or hitching their wagon to it, but to take a weekender project and attempt to build the entire CI system on top of it is insanity. Well, it would have been insanity in a world before having software that sometimes works and sometimes gaslights you became VCs shoveling money. So don't listen to me, I obviously just haven't gotten on the "maybe it works" train 1: https://forgejo.org/docs/latest/user/actions/#:~:text=used%20to%20github%20actions%20but%20they%20are%20not%20and%20will%20never%20be%20identical https://forgejo.org/docs/latest/user/actions/#:~:text=used%2...

omnimus 2y ago

It's also way easier than Gitlab to selfhost. Been running it for some time on small office NAS and it's solid.

jalict 2y ago

Switched from Gitlab to Forgejo at work and it is working fantastic for us. I am also using at home. Using both container registry and self-hosted runners, etc. I was personally very frustrated with ACL and generally inheritance rules in gitlab and it is much more sensible and easy in Forgejo.

dizhn 2y ago

FYI it's a fork of gitea, and like gitea, only a single go binary. Super easy to upgrade. I have been running gitea first and now forgejo under docker. It's literally a 5 minute deal to install once you know how it works.

doubled112 2y ago
I did a bare metal to Docker container migration in about 30 minutes a couple of weeks ago. It’s not a very complicated setup, with few surprises, and this system admin appreciates that.

mdaniel 2y ago

> including CI pipeline You'll want to be cautious, because readme and promises are not software; they're attempting to squat on[1] nektos/act[2] which itself is the 20/80 of GitHub Actions You'll almost certainly be happier using woodpecker[3] or some other "external" CI system so you don't have to hopes-and-prayers your CI system 1: https://code.forgejo.org/forgejo/act https://code.forgejo.org/forgejo/act 2: https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#L81 https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#... and https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#L286 https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#... 3: https://github.com/woodpecker-ci/woodpecker https://github.com/woodpecker-ci/woodpecker (Apache 2)

egometry 2y ago
what do you mean by "squat on"?
- mdaniel 2y ago
  They didn't attempt to build a GitHub Action implementation, they took a known broken one and attempted to duct tape it, so now it's the worst of both worlds: maybe theirs is somehow better, but because everyone in the world knows how terrible act is, they have to say "oh, we built in top of act, but we added some things, fixed others, broke something else, and who knows[1] but good luck to you, our beta testers" Had act been a known working project, maybe it would have been worth the risk of forking it, or hitching their wagon to it, but to take a weekender project and attempt to build the entire CI system on top of it is insanity. Well, it would have been insanity in a world before having software that sometimes works and sometimes gaslights you became VCs shoveling money. So don't listen to me, I obviously just haven't gotten on the "maybe it works" train 1: https://forgejo.org/docs/latest/user/actions/#:~:text=used%20to%20github%20actions%20but%20they%20are%20not%20and%20will%20never%20be%20identical https://forgejo.org/docs/latest/user/actions/#:~:text=used%2...