Compare commits

...
20 Commits
Author SHA1 Message Date
rscmbbng 208c8e4a7c chore: publish 8.4.1+v8.3.1-trixie release 2026-09-30 20:46:55 +02:00
rscmbbng c1fee4d284 chore: update image tags 2026-09-30 20:45:29 +02:00
rscmbbng 072fa33eb2 actually add release notes 2026-09-18 09:58:39 +02:00
rscmbbng 315edede20 chore: publish 8.4.0+v8.3.0-trixie release 2026-09-18 09:57:49 +02:00
rscmbbng 0902f8bab1 chore: update image tags 2026-09-18 09:44:25 +02:00
rscmbbng 31571dbb79 update peertube image to v8.2.4 2026-08-04 10:45:21 +02:00
rscmbbng cc7b20f8ac chore: update image tags 2026-08-04 10:41:25 +02:00
rscmbbng b694ca6df3 publish 8.3.1+v8.2.3-trixie 2026-07-26 11:22:06 +02:00
rscmbbng 144d6a6e3d chore: update image tags 2026-07-26 11:19:40 +02:00
rscmbbng 41ad17d163 upgrade peertube 8.2.2 2026-07-02 19:32:23 +02:00
rscmbbng 9201ac8051 chore: update image tags 2026-07-02 19:22:33 +02:00
rscmbbng 8f3cf17a90 release v.8.2.0+v8.2.1-trixie 2026-06-26 21:55:15 +02:00
rscmbbng 1506db7e0b upgrading config for v8.2.1 2026-06-26 21:49:19 +02:00
rscmbbng 980e247bb5 chore: update image tags 2026-06-26 21:40:33 +02:00
rscmbbng cbf1671295 release 8.1.0+v8.1.8-trixie 2026-06-26 21:38:28 +02:00
rscmbbng c640c6ef17 chore: update image tags 2026-06-26 21:20:41 +02:00
rscmbbng 6eedb2101a 8.0.0+v8.0.2-trixie 2026-06-26 21:19:40 +02:00
rscmbbng c3f9d53fc7 chore: update image tags 2026-06-26 20:19:01 +02:00
3wc dc8cdf8238 chore: publish 7.3.1+v7.3.0-bookworm release 2026-03-26 22:31:36 -04:00
3wc 8eb0e51a98 fix: Correct volume path for postgres… 2026-03-26 22:30:34 -04:00
7 changed files with 86 additions and 6 deletions
+1 -1
View File
@@ -1,6 +1,6 @@
# shellcheck disable=SC2034,SC2145
export NGINX_CONFIG_VERSION=v8
export NGINX_CONFIG_VERSION=v9
export APP_ENTRYPOINT_VERSION=v7
sub_npm() {
+4 -4
View File
@@ -3,7 +3,7 @@ version: "3.8"
services:
web:
image: nginx:1.29.4
image: nginx:1.30.5
networks:
- proxy
- internal
@@ -40,7 +40,7 @@ services:
- "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
app:
image: chocobozzz/peertube:v7.3.0-bookworm
image: chocobozzz/peertube:v8.3.1-trixie
environment:
- PEERTUBE_ADMIN_EMAIL
- PEERTUBE_CONTACT_FORM_ENABLED
@@ -79,7 +79,7 @@ services:
- internal
deploy:
labels:
- "coop-cloud.${STACK_NAME}.version=7.3.0+v7.3.0-bookworm"
- "coop-cloud.${STACK_NAME}.version=8.4.1+v8.3.1-trixie"
db:
image: pgautoupgrade/pgautoupgrade:18-alpine
@@ -90,7 +90,7 @@ services:
secrets:
- db_password
volumes:
- postgres-data:/var/lib/postgresql/data
- postgres-data:/var/lib/postgresql/
networks:
- internal
healthcheck:
+3 -1
View File
@@ -179,7 +179,9 @@ http {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
# Prevent too much proxying, which results in high disk write IO
proxy_max_temp_file_size 50M;
proxy_limit_rate 5M;
proxy_pass http://backend;
+23
View File
@@ -0,0 +1,23 @@
Bumping peertube to v8.0.2
* Ensure storage.uploads directory is set in your `production.yaml` (in `/var/lib/docker/volumes/<app>_app-config/_data`)
* Copy over the [`default.yaml`](https://raw.githubusercontent.com/Chocobozzz/PeerTube/refs/tags/v8.0.2/config/default.yaml) in to `/var/lib/docker/volumes/<app>_app-config/_data/`
* Database migrations of this version can take a long time (up to 30 minutes on an instance with many users/federation actors and a slow database disk)
* 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: 970 in PeerTube startup logs`):
To search the logs:
`abra app logs <app>`
To run the migration:
```
abra app run <app> app bash --user peertube
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-8.0.js```
Full release notes:
https://github.com/Chocobozzz/PeerTube/releases/tag/v8.0.0
https://github.com/Chocobozzz/PeerTube/releases/tag/v8.0.1
https://github.com/Chocobozzz/PeerTube/releases/tag/v8.0.2
+28
View File
@@ -0,0 +1,28 @@
Bumping peertube to v8.1.8
* 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: 1000 in PeerTube startup logs`):
To search the logs:
`abra app logs <app>`
To run the migration, regenerate thumbnails, prune storage:
```
abra app run <app> app bash --user peertube
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-8.1.js
npm run regenerate-thumbnails
npm run prune-storage
```
Full release notes:
https://github.com/Chocobozzz/PeerTube/releases/tag/v8.1.0
https://github.com/Chocobozzz/PeerTube/releases/tag/v8.1.8
+8
View File
@@ -0,0 +1,8 @@
Bumping peertube to v8.2.1
* Copy over the [`default.yaml`](https://raw.githubusercontent.com/Chocobozzz/PeerTube/refs/tags/v8.2.1/config/default.yaml) in to `/var/lib/docker/volumes/<app>_app-config/_data/`
Full release notes:
https://github.com/Chocobozzz/PeerTube/releases/tag/v8.2.0
Massive thanks to 3wc for the help!!
+19
View File
@@ -0,0 +1,19 @@
Bumping peertube to v8.3.0
* If your instance has many videos (local or federated) in the database, automatic migrations at next startup can take several minutes to finish. Plan for a short period of downtime during this upgrade
* You need to manually execute a migration script *after upgrading*, while PeerTube is running and the database migration is complete (Migrations finished. New migration version schema: 1125 in PeerTube startup logs)
To search the logs:
`abra app logs <app>`
To run the migration:
```
abra app run <app> app bash --user peertube
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-8.3.js```
Full release notes:
https://github.com/Chocobozzz/PeerTube/releases/tag/v8.3.0