Right, my #forgejo server is now up and running. Few bumps on the road, but got there in the end.

Next challenge: migrating all users and repos from my #gitlab instance.

Ich betreibe jetzt seit ~2Jahren zwei eigene #forgejo Instanzen. (Eine primäre und ein read-only Fallback)

Jetzt wird es mal Zeit, die primäre Instanz einen Desaster Recovery Prozess zu unterziehen.

Dann muss ich da nur noch "mal eben" einen Runner dran kleben und fertig.

Wenn das so läuft, wie geplant, werde ich meine Repositories auf #GitHub archivieren.

Codeberg/Forgejo can import projects from Gitlab, including source and issues, but it has some rough edges like images in tickets being left behind (e.g. https://codeberg.org/forgejo/forgejo/issues/10760)

Don't suppose anyone has sh/python/nodejs script that can fix up images in imported tickets I could use?

#Codeberg #Forgejo

I've been meaning to ditch gitlab for a year or two or three already, but I guess there's no delaying any more. The only question is whether I'll install Forgejo in a FreeBSD jail or a Linux container...

#gitlab #forgejo #SelfHosting #FreeBSD #Linux

ActivityPub developer guide is available on Codeberg Pages:

https://ap-next.codeberg.page/ap-next/guide.html

I did that mainly to experiment with the stack:

- Marmite, a static site generator written in Rust. Not perfect, but it's the only one that just worked and didn't make me change the directory layout or add extra information to markdown files.
- New Codeberg Pages service, which uses git-pages instead of the deprecated pages-server.
- Forgejo Actions, which came out of beta recently. Unlike Woodpecker CI, actions didn't require extra configuration steps. Deployment from an action to Codeberg Pages is very easy: https://docs.codeberg.org/codeberg-pages/forgejo-actions/

#Forgejo

I'm still surprised by how much snappier my self hosted #forgejo (v15) instance is compared to that well known, exponentionally growing site (that has had lots of downtime lately). And it just works (tm)!

Now onto the next project; getting a personal #Zulip instance up and running. While I honestly think #Mattermost is the better built product, and having lots of home made plugins from when we used it at work, I'm not going to compile my own Android app just to get notifications working.

This post from @alien is exciting! This is very neat stuff. I'm going to go spin up an account when I get to my computer. I'm really curious about the container registry too.

https://fosstodon.org/@alien/116584899021902096

#slackware #git #forgejo

About to expand the MansionNET services for the community by hosting a Git based on Forgejo :)

Looking forward to fist setting it up and then checking out all the projects that will be hosted there!

#selfhosted #forgejo #git #community

Using the Slackware Community Forge

I wanted to share some news with you. After weeks of hard work and being forced to learn new tech from scratch, the Slackware Community Forge, a git software forge, is now available at . It's not just a git repository server but also a Docker container registry! What the Forge? I created this Forge as an autonomous and European based alternative to the popular git forges like…

#Slackware #Codeberg #Forgejo #git

https://blog.slackware.nl/using-the-slackware-community-forge/