forgejo blog post

README.md

@@ -1,3 +1,6 @@
 # trimill.xyz
 
-Source code for the Flask server running [trimill.xyz](https://trimill.xyz). Licensed under [GNU GPLv3](https://www.gnu.org/licenses/gpl-3.0.en.html).
+Source code for the Flask server running [trimill.xyz](https://trimill.xyz). All content licensed under [GNU GPLv3](https://www.gnu.org/licenses/gpl-3.0.en.html), except the following:
+- Symbols from Open Iconic licensed under the [SIL Open Font License](https://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=ofl).
+
+

flaskr/blog/2023-01-16-0.md

@@ -0,0 +1,11 @@
+---
+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/releases/) (/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.