We run our own Forgejo at home and couldn't be happier
Programming
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
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
I set up Forgejo with runners on Coolify on a Hetzner instance for myself, and it’s great. But I use Codeberg for code I want to publish.
Forgejo is working on forge federation, which would enable you to interact with repositories across Forgejo instances (including Codeberg). From my understanding it's still a long way off, but it's a super cool idea.
Because as awesome as Codeberg is, it's still a single point of failure that has to pay bills every month. Hopefully, spreading out the load by hosting projects on separate instances will become a seamless experience once forge federation is working.
Even with federation, the majority of people are still going to use the "main" instance. Look at how many Lemmy communities and users are on .world for example.
I'm glad I got local runners set up already. Beyond that, it should be painless to migrate my projects over, when I get to it that is.
Why Forgejo Actions and not Woodpecker CI, isn’t Woodpecker on Codeberg more stable? Yes, absolutely, in fact the documentation for Forgejo Actions on Codeberg is out of date right now
Waah?
Forgejo Actions will just feel way more familiar coming from GitHub Actions. The UI and YAML syntax is almost identical, and the existing actions ecosystem mostly works as-is on Codeberg.
Ah, ok. I don't care about that.
Setting up woodpecker.
Cow :3
The biggest gap so far is the lack of documentation on how to deal with Jekyll-based Github pages.
Please, Codeberg people, just tell me what's the deal. I don't need drop-in compatibility, but please manage my expectations! Should I use another SSG? Should I move to static HTML pages?
Just tell me, please!
You can just run the build locally and push the output to a branch. Same as people using other SSGs with GitHub pages have been doing for ages
I know what I "can just" do.
It's just missing most of the point of a shared hosting service then.
Whar? GitHub Pages is a static host. Jekyll is a static site generator. The only thing you don't get is a free CI deploy pipeline, but you don't need that to deploy a website.
If you haven't gotten the point by now, it's not a good investment of my time. Bye.
I predict most users will just stay on Github, since they've been there already.
I can already assert my intentions to stay on GitHub, even with all the AI and spyware and stealing data and whatever, all my code that is public is also available for anyone else to train a model, and all of my private repos are just backups for shit that's probably not worth anything, all of my valuable shit I keep backed up my way. I guess if you were using GitHub to store your valuables then you'd be pissed but there's the taking-responsibility part.
I moved quite a while ago and have no intentions of returning to Github.
You're on lemmy, i'm not talking about users like you that know better, but all the other users that don't and that's a majority of the GitHub users.
And? Why would I give a fuck?
So desperate about what other people think ... are you an American by chance?



