Compare commits

...
Author SHA1 Message Date
fauno 08f5f4424c fix: autogenerate peertube secret
continuous-integration/drone/pr Build is failing
closes #22
2026-02-25 12:35:12 -03:00
3wordchant 528306134a Merge pull request 'fix typo' (#20) from Numerica/peertube:main into main
continuous-integration/drone/push Build is failing
Reviewed-on: #20
2026-02-25 04:39:18 +00:00
Roberto Soto 1b7a6bdf3d fix typo
continuous-integration/drone/pr Build is failing
2026-02-23 10:59:49 -03:00
3wc 67fab632a8 chore: publish 7.2.0+v7.3.0-bookworm release
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is failing
2025-12-27 20:17:28 -05:00
rscmbbng ba4fcf2e11 update label
continuous-integration/drone/push Build is passing
2025-10-02 22:08:24 +02:00
rscmbbng 2b763f0719 Release notes for 7.1.0+v7.1.1-bookworm 2025-10-02 22:05:40 +02:00
rscmbbng 9e716979d5 chore: publish 7.1.0+v7.1.1-bookworm release
continuous-integration/drone/tag Build is passing
2025-10-02 22:01:31 +02:00
rscmbbng 8eda97112f chore: publish 7.0.0+v7.0.1-bookworm release
continuous-integration/drone/tag Build is passing
2025-10-02 21:49:20 +02:00
rscmbbng 44d1d7a906 release notes 6.1.0+v6.3.3-bookworm
continuous-integration/drone/push Build is passing
2025-10-02 21:39:22 +02:00
rscmbbng e47fc0dbd3 chore: publish 6.1.1+v6.3.3-bookworm release
continuous-integration/drone/tag Build is passing
2025-10-01 11:04:13 +02:00
rscmbbng 20a13e075f chore: publish 6.1.0+v6.3.3-bookworm release
continuous-integration/drone/tag Build is passing
2025-10-01 10:57:57 +02:00
7 changed files with 75 additions and 39 deletions
+1 -1
View File
@@ -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
#
+4 -6
View File
@@ -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
+1 -5
View File
@@ -1,12 +1,8 @@
# shellcheck disable=SC2034,SC2145
export NGINX_CONFIG_VERSION=v5
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"
+5 -5
View File
@@ -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.0.4-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.0.2+v6.0.4-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:
+28 -22
View File
@@ -46,8 +46,15 @@ http {
try_files /dev/null @api;
}
location = /api/v1/videos/upload {
limit_except POST HEAD { deny all; }
location ~ ^/api/v1/users/[^/]+/imports/import-resumable$ {
client_max_body_size 0;
proxy_request_buffering off;
try_files /dev/null @api;
}
location ~ ^/api/v1/videos/(upload|([^/]+/studio/edit))$ {
limit_except POST HEAD { deny all; }
# This is the maximum upload size, which roughly matches the maximum size of a video file.
# Note that temporary space is needed equal to the total size of all concurrent uploads.
@@ -59,6 +66,13 @@ http {
try_files /dev/null @api;
}
location ~ ^/api/v1/runners/jobs/[^/]+/(update|success)$ {
client_max_body_size 12G; # default is 1M
add_header X-File-Maximum-Size 8G always; # inform backend of the set value in bytes before mime-encoding (x * 1.4 >= client_max_body_size)
try_files /dev/null @api;
}
location ~ ^/api/v1/(videos|video-playlists|video-channels|users/me) {
client_max_body_size 3M; # default is 1M
add_header X-File-Maximum-Size 2M always; # inform backend of the set value in bytes before mime-encoding (x * 1.4 >= client_max_body_size)
@@ -93,6 +107,11 @@ http {
try_files /dev/null @api_websocket;
}
# Plugin websocket routes
location ~ ^/plugins/[^/]+(/[^/]+)?/ws/ {
try_files /dev/null @api_websocket;
}
##
# Performance optimizations
# For extra performance please refer to https://github.com/denji/nginx-tuning
@@ -111,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
@@ -155,11 +175,13 @@ http {
location ~ ^(/static/(webseed|web-videos|streaming-playlists)/private/)|^/download {
#We can't rate limit a try_files directive, so we need to duplicate @api
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_limit_rate 5M;
proxy_pass http://backend;
}
@@ -167,13 +189,7 @@ http {
location ~ ^/static/(webseed|web-videos|redundancy|streaming-playlists)/ {
limit_rate_after 5M;
# Clients usually have 4 simultaneous webseed connections, so the real limit is 3MB/s per client
set $peertube_limit_rate 800k;
# Increase rate limit in HLS mode, because we don't have multiple simultaneous connections
if ($request_uri ~ -fragmented.mp4$) {
set $peertube_limit_rate 5M;
}
set $peertube_limit_rate 5M;
# Use this line with nginx >= 1.17.0
limit_rate $peertube_limit_rate;
@@ -194,23 +210,13 @@ http {
add_header Access-Control-Allow-Origin '*';
add_header Access-Control-Allow-Methods 'GET, OPTIONS';
add_header Access-Control-Allow-Headers 'Range,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
add_header X-Cache-Status $upstream_cache_status;
add_header X-Cache-Range $slice_range;
add_header X-Fuuu ok;
add_header X-Accel-Expires 604800;
# Don't spam access log file with byte range requests
access_log off;
}
aio threads;
# Enabling the sendfile directive eliminates the step of copying the data into the buffer
# and enables direct copying data from one file descriptor to another.
sendfile on;
sendfile_max_chunk 1M; # prevent one fast connection from entirely occupying the worker process.
# should be > 800k.
sendfile_max_chunk 1M; # prevent one fast connection from entirely occupying the worker process. should be > 800k.
aio threads;
{{ if eq (env "NGINX_WEBSEED_PROXY_ENABLED") "1" }}
proxy_connect_timeout 70;
+25
View File
@@ -0,0 +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
+11
View File
@@ -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