Programming

19722 readers

80 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Codeberg, self-hosting Gitea, or something else? (lemmy.world)

submitted 3 days ago* (last edited 2 days ago) by scheep@lemmy.world to c/programming@programming.dev

19 comments fedilink hide all child comments

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 (https://username.codeberg.page/repo-name/)

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

you are viewing a single comment's thread
view the rest of the comments

[–] kensand@sopuli.xyz 8 points 2 days ago (2 children)

https://forgejo.org/compare-to-gitea/

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

[–] scheep@lemmy.world 2 points 2 days ago* (last edited 2 days ago) (1 children)

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 5 points 2 days ago (1 children)

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 1 points 2 days ago

ahh okay :0

[–] scheep@lemmy.world 1 points 2 days ago

ah okay