gitea on top

Caddyfile

@@ -12,5 +12,5 @@ post.yaoi.dog {
 }
 
 git.yaoi.dog {
-    reverse_proxy forgejo:3000
+    reverse_proxy gitea:3000
 }

README.md

@@ -41,7 +41,7 @@ specifics for everything
 | `A`   | `@`       | `<ip>`                      | apex domain                |
 | `A`   | `mail`    | `<ip>`                      | mailserver                 |
 | `A`   | `post`    | `<ip>`                      | webmail                    |
-| `A`   | `git`     | `<ip>`                      | forgejo                    |
+| `A`   | `git`     | `<ip>`                      | gitea                      |
 | `CAA` | `@`       | `0 issue "letsencrypt.org"` | allow caddy to issue certs |
 
 ### caddy
@@ -97,7 +97,7 @@ todo
 
 - https://bulwarkmail.org/docs
 
-### forgejo
+### gitea
 
 todo
 
@@ -134,7 +134,7 @@ the restore process is kind of fucked up but doable
 
 - further secure the server (ratelimiting, hardening...)
 - more services
-  - ~~forgejo (need to change host ssh port)~~
+  - ~~gitea (need to change host ssh port)~~
   - vaultwarden
 - ~~tie all services together with an sso~~
 - use postgres for everything

docker-compose.yml

@@ -54,9 +54,9 @@ services:
     depends_on:
       - stalwart
 
-  forgejo:
-    image: codeberg.org/forgejo/forgejo:16
-    container_name: forgejo
+  gitea:
+    image: docker.gitea.com/gitea:1.27.0
+    container_name: gitea
     restart: unless-stopped
     environment:
       - USER_UID=1000
@@ -64,7 +64,7 @@ services:
     ports:
       - "22:22"
     volumes:
-      - forgejo-data:/data
+      - gitea-data:/data
     networks:
       - services
 
@@ -77,7 +77,7 @@ volumes:
   bulwark-config:
   bulwark-state:
   bulwark-telemetry:
-  forgejo-data:
+  gitea-data:
 
 networks:
   services: