61–70 of 87 posts
For info: there was some drama a while back [0], [1] and some (a lot?) of the community/devs went to https://forgejo.org/ Seemed to me like they had a point and it's worth considering following that project [2] instead. [0] https://gitea-open-letter.coding.social/ [1] https://news.ycombinator.com/item?id=33372471 [2] https://codeberg.org/forgejo/forgejo
What are the current thoughts on Gitea vs Forgejo? I'm thinking of migrating from a self-hosted Gitlab to one of them in the near future. The way Gitea was taken over leaves a bad taste in my mouth so I'm leaning towards Forgejo, but it's not really clear to me if that's the right choice.
Earlier quoted context omitted.
Quick note that the forked project doesn't have the CI feature released in 1.9, which is the primary subject of this thread.
I assume they will follow up with their own 1.19 release soon. The blog below indicates they will have the CI feature. https://forgejo.org/2023-02-27-forgejo-actions/
Wow. Great progress! Recently, I was wondering why gitea does not have a GitHub Actions alternative. What a timing. BTW, a colleague of mine told me that GitHub Actions wasn't supposed to be a CI/CD alternative at the time when it was released. I couldn't find any note on that online. Is it true?
Not sure what you mean by that, what was it supposed to be then?
Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system.
Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system.
Earlier quoted context omitted.
I assume they will follow up with their own 1.19 release soon. The blog below indicates they will have the CI feature. https://forgejo.org/2023-02-27-forgejo-actions/
It seems that they have "soft forked" act as well. I worry that they will spend more time maintaining all their forks than doing any original development...
"This is a custom fork of nektos/act, for the purpose of serving act_runner.
It cannot be used as command line tool anymore, but only as a library.
It's a soft fork, which means that it will tracking the latest release of nektos/act."
very excited about Actions. For several months I've been using a home server Gitea for a Unity project version control, because the project size is far too large for github/gitlab etc. So far everything about it has been excellent, and it's only getting better!
Are you working on anything publicly available? I'm looking for something new to play :)
Disclaimer: I am a part of the Gitea TOC, and am employed to work on Gitea.
As a novice at self-hosting, I previously attempted to use it, but got stuck as I didn't understand MySQL, and learning it just for Gitea was too much. However, I've had some progress with with another database recently, so I would like to give Gitea another try soon.
For small personal deployments, using SQLite as a database is usually sufficient. This means you don't need a fullblown SQL server, instead the whole database consists of a single file.
Earlier quoted context omitted.
From what I, as an outsider, could see, it seemed like most contributors stayed with gitea. At this point forgejo is just a soft-fork as well, so there really isn't any reason or hurry to switch (yet) in my opinion. Though it did stand out that they are migrating stuff from gitea.io to gitea.com, as mentioned in this blog post.
Out of curiosity, why did that stand out? We've had the .com domain for a little while, so now we're starting to consolidate things to it.