Codeberg, self-hosting Gitea, or something else?
from scheep@lemmy.world to programming@programming.dev on 21 Apr 23:39
https://lemmy.world/post/28539665

It seems that GitHub is being blocked in my region as well as other options from U.S. based companies (e.g. GitLab)

Where should I migrate my repos? Codeberg is an option as it’s Europe based so isn’t blocked in my region. Codeberg Pages is also nice to have. However, Codeberg seems to push for excluding proprietary software dependencies, which might limit the kinds of projects I can do.

Another option is to self-host Gitea, I could use my old laptop for that. Gitea doesn’t have a GitHub pages, but there seems to be third-party plugins that allow that. The downside with self-hosting (for me) is that it means I’m unable to collaborate with others (since it’ll be local) and I can’t easily share my projects. It will also probably be harder to set up.

What other options are there, or are these two the best options for me?

edit: decided on Codeberg, how do I make my static pages to work with Codeberg Pages? I’ve switched to a “pages” branch and the website doesn’t work (username.codeberg.page/repo-name/)

How do I make static pages work with Codeberg???

#programming

threaded - newest

deathmetal27@lemmy.world on 21 Apr 23:44 next collapse

Forgejo. It is a fork of Gitea.

kensand@sopuli.xyz on 21 Apr 23:52 next collapse

A better* fork of Gitea!

scheep@lemmy.world on 21 Apr 23:57 collapse

how so? Is it easier to set up or have more features? What’s the difference? please educate me :D

3h5Hne7t1K@lemmy.world on 22 Apr 00:34 next collapse

Not sure if its better, did both and i havent noticed much difference. Forgejo runs codeberg though and is maintained by them. Also has CI with forgejo actions.

mbirth@lemmy.ml on 22 Apr 02:27 collapse

And Gitea has Gitea Actions. The big difference - and also the sole reason ForgeJo was forked - is that Gitea has a business behind it that allows them to sell support hours to other businesses. And then use the money to progress Gitea. Similar to how Zabbix and others do it. But the community decided that this is a bad thing and moved to ForgeJo.

Dunstabzugshaubitze@feddit.org on 22 Apr 06:20 collapse

gittea ltd was founded without adhering to the governance model gittea had and also claimed copyright on atleast the name and logo of gittea. many felt a non-profit would be a better way to organize development and thats how codeberg e.v. came to be.

the problem is not, and never was offering support and service against money, you can right now start selling forgejo if you’d desire to, it was allways about how the project itself should be organized.

mbirth@lemmy.ml on 22 Apr 08:30 collapse

While a non-profit sounds very honourable, I personally think Gitea has the more future-proof model. In fact, Gitea Actions was something they got commissioned for and were allowed to open source it as well.

This is basically how I think about it. (Not my comment.)

But we’ll see…

mbirth@lemmy.ml on 22 Apr 00:35 collapse

how so?

I’d like to get educated as well, please. So far, ForgeJo doesn’t seem to have any specific advantage over Gitea. (And the name couldn’t be worse…)

scheep@lemmy.world on 21 Apr 23:52 collapse

what’s the difference?

kensand@sopuli.xyz on 22 Apr 01:40 collapse

forgejo.org/compare-to-gitea/

CI actions and actually being free software are my main notes, but there are many reasons.

scheep@lemmy.world on 22 Apr 04:21 next collapse

ah okay

scheep@lemmy.world on 22 Apr 04:23 collapse

wait…how is forgejo developed on forgejo? If there is no forgejo to begin with, how did they begin developing?

edit: maybe they switched from github to forgejo a bit later?

kensand@sopuli.xyz on 22 Apr 10:21 collapse

This process is called ‘bootstrapping’, and is actually quite common in software. For example, the C compiler is written in C. The first iteration of the C compiler was written by hand in assembly code with a very limitted feature set, and that compiler was then used to compile the next iteration, allowing the second version (I’m not sure it was actually the second version; there may have been a few iterations in assembly) to be written in C itself.

For Forgejo, you dont actually need Forgejo to build Forgejo; just a computer with the Go compiler and any other dependencies. Then, once you have the first version, you can publish the code you have on Forgejo. Nothing too crazy there 🙂

This also leads to ‘dogfooding’, which is a whole other term…

scheep@lemmy.world on 22 Apr 10:59 collapse

ahh okay :0

solrize@lemmy.world on 22 Apr 01:27 next collapse

www.chiark.greenend.org.uk/…/git-no-forge/

Just plain git.

Ephera@lemmy.ml on 22 Apr 02:22 collapse

There’s also an official guide for this: git-scm.com/…/Git-on-the-Server-The-Protocols

kensand@sopuli.xyz on 22 Apr 01:59 next collapse

Since you’re a bit concerned about self hosting and collaboration, I would recommend Codeberg - they are a non-profit based in Germany with widespread support and, as far as I know, is the public Forgejo instance with the largest user base.

If you want, you can also host your own Forgejo instance and mirror your Codeberg repos to it. That way you can have two copies of your data, just in case Codeberg ever goes offline.

You could also potentially use Gitlab, but I would personally prefer something Forgejo based. Forgejo has been much more responsive/snappier in my opinion; Forgejo is primarily written in Go, while Gitlab is mostly Ruby.

scheep@lemmy.world on 22 Apr 02:20 collapse

ah okay I’ll try that

Ephera@lemmy.ml on 22 Apr 02:37 collapse

However, Codeberg seems to push for excluding proprietary software dependencies, which might limit the kinds of projects I can do.

Well, they ask for software projects to be themselves under a FOSS license. If you can isolate the proprietary dependencies, you could still open-source the code.

Of course, you could also consider using Codeberg for all your open-source projects and then self-host a Git server for your proprietary projects.