Repository navigation
PeerTube #2122
Description
Name of the Script
PeerTube
Script Type
CT (LXC Container)
Does this script support arm64?
arm64 supported
📋 Script Details
PeerTube is a federated, self-hosted video platform — peer-to-peer distribution via WebTorrent, ActivityPub federation with the rest of the fediverse.
- Uses the prebuilt release, not a source build:
prebuildmode withpeertube-v*.zip._deploy_unpacked_archivestrips the single top-level dir, so the release lands directly in/opt/peertube. Thennpm run install-node-dependencies -- --production. - Adapted from upstream
support/doc/production.mdto the project conventions: runs as root instead of apeertubeuser,/optinstead of/var/www/peertube. - Config:
default.yamlcopied from the release, plus a minimalproduction.yamlthat only overrides what matters (PeerTube merges production over default). All 19storage:keys are set to absolute/opt/peertube_data/storage/...paths so nothing lands in the app dir thatCLEAN_INSTALLwipes. listen.hostnameis set to0.0.0.0— the upstream example defaults to127.0.0.1, which would make the container unreachable from outside.- DB is
peertube_prodwithpg_trgmandunaccentviaPG_DB_EXTENSIONS, matching thedatabase.suffix: '_prod'convention. - Note: PeerTube does not support changing
webserver.hostnameafter content exists — set the final domain before first use. Federation needs HTTPS; the install is plain HTTP on :9000 for initial setup. Both flagged as warnings. - Initial
rootpassword is generated on first start and printed to the journal.
Activity
github-actions commentedon Aug 3, 2026
The PeerTube script is ready for testing:
Default credentials:
Username: root
The initial 'root' password is generated on first start and written to the log. Read it with: journalctl -u peertube | grep -i 'User password'
PeerTube does not support changing the webserver hostname after the fact - it is a documented, risky operation. Set webserver.hostname in /opt/peertube_data/config/production.yaml to your final domain BEFORE creating any content, then restart the service.
For federation and normal use PeerTube needs HTTPS on a public domain. The install is configured for plain HTTP on port 9000 for initial setup; put it behind a TLS reverse proxy and set webserver.https to true and port to 443.
Videos, thumbnails and logs live in /opt/peertube_data/storage, the configuration in /opt/peertube_data/config, and metadata in the PostgreSQL database 'peertube_prod'. Transcoding is CPU-heavy - give the container more cores if you upload a lot.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1533830202541473792
github-actions commentedon Sep 2, 2026
A PR has been created for peertube: community-scripts/ProxmoxVE#16966
MickLesk commentedon Sep 2, 2026
Merged with #16966 in ProxmoxVE