trimill.xyz/flaskr/blog/2023-01-16-0.md
2023-01-16 21:01:03 -05:00

12 lines
1.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
title: Forgejo
desc: Updates regarding g.trimill.xyz
timestamp: 2023-01-16T20:00:00-05:00
---
Recently, [Gitea](https://gitea.io/) (which I had previously been using to self-host [my git server](https://g.trimill.xyz/)) has [found itself](https://blog.gitea.io/2022/10/open-source-sustainment-and-the-future-of-gitea/) under the control of a for-profit organization. As often happens after occurrences like these, it was quickly forked into [Forgejo](https://forgejo.org/) (/forˈd͡ʒe.jo/), which is community-governed rather than being run by a corporation. (sidenote: gitea itself was originally a fork of another project called [gogs](https://gogs.io/) and was created due to disagreements over governance. oh how history repeats itself!)
Switching from Gitea to Forgejo proved to be very easy. Forgejo isn't yet available in any Debian repos, so I had to install it manually and create a new systemd service for it (this can be done trivially by copying and modifying `gitea.service`). After this was done, everything Just Worked™ and through the whole process I only experienced a minute or two of downtime.
So far Forgejo includes some new themes and privacy enhancements, but they plan on adding [ForgeFed](https://forgefed.org/) support soon which will be quite cool.