fix: autogenerate peertube secret

closes #22

.env.sample

@@ -15,7 +15,7 @@ SECRET_DB_PASSWORD_VERSION=v1
 
 # Comment out these lines if you want to store the peertube secret in a config file instead of a docker secret
 COMPOSE_FILE="$COMPOSE_FILE:compose.peertube-secret.yml"
-SECRET_PEERTUBE_SECRET_VERSION=v1
+SECRET_PEERTUBE_SECRET_VERSION=v1 # length=32
 
 ## Webseed backend
 #

README.md

@@ -21,12 +21,10 @@ An ActivityPub-federated video streaming platform using P2P directly in your web
 1. Set up Docker Swarm and [`abra`]
 2. Deploy [`coop-cloud/traefik`]
 3. `abra app new peertube`
-4. `abra app cmd -l YOURAPPDOMAIN generate_secret`
-5. `abra app secret generate YOURAPPDOMAIN -a`
-6. `abra app config YOURAPPDOMAIN` - be sure to change `DOMAIN` to something that resolves to
-   your Docker swarm box
-7. `abra app deploy YOURAPPDOMAIN`
-8. Open the configured domain in your browser to finish set-up
+4. `abra app secret generate YOURAPPDOMAIN -a`
+5. `abra app config YOURAPPDOMAIN` - be sure to change `DOMAIN` to something that resolves to your Docker swarm box
+6. `abra app deploy YOURAPPDOMAIN`
+7. Open the configured domain in your browser to finish set-up
 
 ## Host-mode networking
 

abra.sh

@@ -1,12 +1,8 @@
 # shellcheck disable=SC2034,SC2145
 
-export NGINX_CONFIG_VERSION=v7
+export NGINX_CONFIG_VERSION=v8
 export APP_ENTRYPOINT_VERSION=v7
 
-generate_secret() {
-  abra app secret insert "$APP_NAME" peertube_secret v1 "$(openssl rand -hex 32)" --chaos
-}
-
 sub_npm() {
   abra__service_="app"
 

compose.yml

@@ -3,7 +3,7 @@ version: "3.8"
 
 services:
   web:
-    image: nginx:1.27.4
+    image: nginx:1.29.4
     networks:
       - proxy
       - internal
@@ -40,7 +40,7 @@ services:
         - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
 
   app:
-    image: chocobozzz/peertube:v6.3.3-bookworm
+    image: chocobozzz/peertube:v7.3.0-bookworm
     environment:
       - PEERTUBE_ADMIN_EMAIL
       - PEERTUBE_CONTACT_FORM_ENABLED
@@ -79,10 +79,10 @@ services:
       - internal
     deploy:
       labels:
-        - "coop-cloud.${STACK_NAME}.version=6.1.1+v6.3.3-bookworm"
+        - "coop-cloud.${STACK_NAME}.version=7.2.0+v7.3.0-bookworm"
 
   db:
-    image: pgautoupgrade/pgautoupgrade:17-alpine
+    image: pgautoupgrade/pgautoupgrade:18-alpine
     environment:
       - POSTGRES_USER=peertube
       - POSTGRES_DB=peertube
@@ -100,7 +100,7 @@ services:
       retries: 10
 
   cache:
-    image: redis:7-alpine
+    image: redis:8-alpine
     volumes:
       - redis-data:/data
     networks:

nginx.conf.tmpl

@@ -130,7 +130,8 @@ http {
                       font/truetype
                       font/opentype
                       application/vnd.ms-fontobject
-                      image/svg+xml;
+                      image/svg+xml
+                      application/xml;
     gzip_min_length   1000; # default is 20 bytes
     gzip_buffers      16 8k;
     gzip_comp_level   2; # default is 1

release/6.1.0+v6.3.3-bookworm

@@ -1 +1,25 @@
- 
+Before upgrading:
+
+You might need to migrate some data, depending on your setup:
+> Important for Docker admins If you enabled the "Keep a version of the input file" configuration, files may have been stored in the container instead of the host volume. To prevent data loss, you must copy the files on the host before upgrading using docker compose cp peertube:/app/storage/original-video-files docker-volume/data
+
+If you are upgrading from earlier versions, double check the configs `default.yml` and `production.yaml` as new config keys have been added but we are (currently) not tracking that file here (see issue: https://git.coopcloud.tech/coop-cloud/peertube/issues/17). 
+
+You can find the production.yaml.example here:
+https://github.com/Chocobozzz/PeerTube/blob/v6.3.3/config/production.yaml.example
+
+After upgrading:
+You need to manually execute a migration script after your upgrade while PeerTube is running and the database migration is complete (`Migrations finished. New migration version schema: 865` in PeerTube startup logs, this migration script may take a while).
+
+To search the logs: 
+`abra app logs <app>`
+
+To execute the migration: 
+
+```abra app run <app> app bash
+export ARGS="-e NODE_CONFIG_DIR=/config -e NODE_ENV=production"
+export PEERTUBE_DB_PASSWORD=$(cat /run/secrets/db_password)
+node dist/scripts/migrations/peertube-6.3.js```
+
+You can find the full release notes here:
+https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md#important-notes-5

release/7.1.0+v7.1.1-bookworm

@@ -0,0 +1,11 @@
+> Due to a bug in the remote video thumbnail update, we recommend running the prune storage script to clean up the filesystem
+
+```abra app run <app> app bash
+export ARGS="-e NODE_CONFIG_DIR=/config -e NODE_ENV=production"
+export PEERTUBE_DB_PASSWORD=$(cat /run/secrets/db_password)
+npm run prune-storage```
+
+> If you are using object storage, you will need to create the captions bucket or configure PeerTube to use an existing one in the configuration file or using environment variables if you use Docker (PEERTUBE_OBJECT_STORAGE_CAPTIONS_BUCKET_NAME, PEERTUBE_OBJECT_STORAGE_CAPTIONS_PREFIX, PEERTUBE_OBJECT_STORAGE_CAPTIONS_BASE_URL)
+
+See release notes: https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md#v710
+