feat: support Git LFS on plain gitea

Add an opt-in compose.lfs.yml that mounts the lfs_jwt_secret secret and
enables GITEA_LFS_START_SERVER for plain gitea (forgejo already bundles
LFS). Emit LFS_JWT_SECRET in app.ini whenever the LFS server is on so the
JWT secret is stable across redeploys instead of being regenerated on
every restart (app.ini is a read-only config mount).

Bump version 3.5.2 -> 3.6.0.

README.md

@@ -15,7 +15,7 @@
 
 ## Basic usage
 
-1. [Set up Docker Swarm and `abra`][operators-tutorial]
+1. Set up Docker Swarm and [`abra`][abra]
 2. Deploy [`coop-cloud/traefik`][cc-traefik]
 3. `abra app new gitea --secrets` (optionally with `--pass` if you'd like
    to save secrets in `pass`)
@@ -23,15 +23,12 @@
    your Docker swarm box
 5. `abra app deploy YOURAPPDOMAIN`
 
-[operators-tutorial]: https://docs.coopcloud.tech/operators/tutorial/
-[cc-traefik]: https://git.coopcloud.tech/coop-cloud/traefik/
-
 ## Create first user
 
 Run
 
 ```bash
-abra app run YOURAPPNAME app -- gitea -c /etc/gitea/app.ini admin user create --username USERNAME --admin --random-password --email EMAIL
+abra app run YOURAPPNAME app gitea -c /etc/gitea/app.ini admin user create --username USERNAME --admin --random-password --email EMAIL
 ```
 
 See the [Gitea command-line documentation](https://docs.gitea.io/en-us/command-line/) for more options.  Make sure not to forget the `-c /etc/gitea/app.ini`.
@@ -39,34 +36,25 @@ See the [Gitea command-line documentation](https://docs.gitea.io/en-us/command-l
 ## Enable SSH
 
 You most certainly want to be able to access your repository over SSH.  To do so, make sure you uncomment the right lines in the configuration for `traefik`.
-
-```sh
+```
 abra app config YOURTRAEFIKAPP
 ```
-
 There uncomment or add these lines:
-
-```sh
+```
 GITEA_SSH_ENABLED=1
 COMPOSE_FILE="compose.yml:compose.gitea.yml"
 ```
-
 Then redeploy traefik:
-
-```sh
+```
 abra app undeploy YOURTRAEFIKAPP
 abra app deploy YOURTRAEFIKAPP
 ```
-
 You might need to wait a bit.  To check if it worked, you can run
-
-```sh
+```
 telnet my.gitea.example.com 2222
 ```
-
 Once you have added a public SSH key, you can check that you can connect to your gitea server with
-
-```sh
+```
 ssh -T -p 2222 git@my.gitea.example.com
 ```
 

abra.sh

@@ -1,4 +1,4 @@
-export APP_INI_VERSION=v22
+export APP_INI_VERSION=v21
 export DOCKER_SETUP_SH_VERSION=v1
 export PG_BACKUP_VERSION=v1
 

compose.postgres.yml

@@ -10,7 +10,7 @@ services:
     secrets:
       - db_password
   db:
-    image: postgres:15.18
+    image: postgres:15.13
     deploy:
       labels:
         backupbot.backup.pre-hook: "/pg_backup.sh backup"

compose.yml

@@ -3,7 +3,7 @@ version: "3.8"
 
 services:
   app:
-    image: "gitea/gitea:1.26.2-rootless"
+    image: "gitea/gitea:1.24.2-rootless"
     configs:
       - source: app_ini
         target: /etc/gitea/app.ini
@@ -71,7 +71,7 @@ services:
     deploy:
       update_config:
         failure_action: rollback
-        order: stop-first
+        order: start-first
       labels:
         - "backupbot.backup=${ENABLE_BACKUPS:-true}"
         - "traefik.enable=true"
@@ -88,7 +88,7 @@ services:
         - "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolalloworiginlist=https://${GITEA_CORS_ALLOW_DOMAIN}"
         - "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolmaxage=100"
         - "traefik.http.middlewares.${STACK_NAME}_cors.headers.addvaryheader=true"
-        - coop-cloud.${STACK_NAME}.version=3.6.1+1.26.2-rootless
+        - coop-cloud.${STACK_NAME}.version=3.6.0+1.24.2-rootless
 
 
 networks: