PeerTube on Storm Buckets
PeerTube can keep its video on object storage. Point it at a Storm Bucket and it uploads every video and HLS playlist over S3, while viewers stream straight from the bucket's public URL.
NorthTube runs this way. Its videos live in a Storm Bucket served at northtube.stormsites.ca, and the PeerTube instance holds only the database and the web app. The steps below are the same setup, with placeholders for your bucket.
What you need first
-
PeerTube 8.1 or later. Storm Buckets is path-style only, and PeerTube added
force_path_stylein 8.1. Run 8.3 or later, which fixed a path-style URL bug. Installing PeerTube itself is PeerTube's own guide. -
At least one bucket. See Getting Started.
-
An access key for that bucket, the bucket's admin key or an account key attached to it. See Managing Access Keys.
-
Static hosting enabled on the bucket, and the
stormsites.caURL it gives you. See Static hosting. Viewers read video from this URL, so PeerTube has to know it.
One bucket holds everything. Web videos and HLS playlists live under two prefixes in the same bucket, so it takes one Static Hosting toggle and one URL. Those two carry playback and must be on S3. User exports, original video files and captions are optional. Leave them off and PeerTube keeps that content on the server's local disk.
Configure object storage
PeerTube reads its object storage config from .env on a Docker install, or from config/production.yaml on bare metal. Pick your install method, type your bucket name, choose one bucket or a bucket per content type, and copy the result.
PEERTUBE_OBJECT_STORAGE_ENABLED=true
PEERTUBE_OBJECT_STORAGE_ENDPOINT=https://montreal-1.buckets.stormdevelopments.ca
PEERTUBE_OBJECT_STORAGE_REGION=montreal-1
PEERTUBE_OBJECT_STORAGE_FORCE_PATH_STYLE=true
PEERTUBE_OBJECT_STORAGE_CREDENTIALS_ACCESS_KEY_ID=<your key id>
PEERTUBE_OBJECT_STORAGE_CREDENTIALS_SECRET_ACCESS_KEY=<your secret>
PEERTUBE_OBJECT_STORAGE_WEB_VIDEOS_BUCKET_NAME=your-bucket
PEERTUBE_OBJECT_STORAGE_WEB_VIDEOS_PREFIX=web-videos/
PEERTUBE_OBJECT_STORAGE_WEB_VIDEOS_BASE_URL=https://your-subdomain.stormsites.ca
PEERTUBE_OBJECT_STORAGE_STREAMING_PLAYLISTS_BUCKET_NAME=your-bucket
PEERTUBE_OBJECT_STORAGE_STREAMING_PLAYLISTS_PREFIX=streaming-playlists/
PEERTUBE_OBJECT_STORAGE_STREAMING_PLAYLISTS_BASE_URL=https://your-subdomain.stormsites.ca
# Garage has no per-object ACLs. Empty disables them.
PEERTUBE_OBJECT_STORAGE_UPLOAD_ACL_PUBLIC=
PEERTUBE_OBJECT_STORAGE_UPLOAD_ACL_PRIVATE=
-
REGION=montreal-1. The region is your endpoint's name, never an AWS
region orgarage. The S3 signature includes the region, so a wrong value
fails every request. -
FORCE_PATH_STYLE=true. Without it, PeerTube builds every request as
bucket.montreal-1.buckets.stormdevelopments.ca, which does not exist. -
BASE_URL=https://<your-subdomain>.<endpoint>.stormsites.ca. The public URL viewers
fetch from. Left unset, PeerTube hands out URLs on the private S3 endpoint,
which the public cannot read. Every content type points at the same
subdomain, and the prefix keeps them apart. -
Empty
UPLOAD_ACLvalues. Garage has no per-object ACLs. Commented out,
PeerTube still sends itspublic-readdefault, so set both empty, ornull
inproduction.yaml.
Restart and upload
Restart PeerTube to load the new config, then upload a video.
Docker:
docker compose down && docker compose up -d
Bare metal (systemd):
sudo systemctl restart peertube
Upload a clip through the web UI and let it finish transcoding. Under Administration, then Jobs, VIDEO-TRANSCODING jobs run on local disk first, then a MOVE-TO-OBJECT-STORAGE job copies each finished file to the bucket.

Once the move jobs read COMPLETED, the files are in Storm Buckets.

Open the bucket's Files tab in your dashboard. You should see objects under web-videos/ and, once HLS transcoding finishes, under streaming-playlists/.
PeerTube's default transcoding is HLS-only, so web-videos/ may hold only a
small audio file. Turn on Web Videos under Administration, Settings,
Transcoding, then re-transcode existing clips to get standalone MP4s there.
Move videos you already have
Videos uploaded before the switch stay on local disk until you move them.
Bare metal, from /var/www/peertube/peertube-latest as the peertube user:
NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production \
npm run create-move-video-storage-job -- --to-object-storage --all-videos
Docker:
docker compose exec -u peertube peertube \
npm run create-move-video-storage-job -- --to-object-storage --all-videos
Each video becomes a MOVE-TO-OBJECT-STORAGE job. --to-file-system moves them back.
Verify playback
Play a video in a browser. If it streams start to finish and switches resolutions, PeerTube is backed by Storm Buckets end to end, and nothing proxies through the app server.
The page loads from your instance host, while the video and HLS segments come from your stormsites.ca URL, so playback is a cross-origin request. Storm Buckets sets the CORS header on public responses, so HLS loads with no extra configuration.
Private videos
Garage has no per-object ACLs, so a private or unlisted video's files sit in the same publicly served bucket as everything else. PeerTube keeps them out of listings and pages, but anyone holding a file's URL can fetch it. If your instance hosts private video, keep those videos on local disk or run a separate instance for them.
Next steps
-
Managing Access Keys to rotate or scope
the key PeerTube uploads with. -
Custom Domains to serve
video from your own domain. -
Connecting S3 Tooling for the full
endpoint, region and client field reference. -
Media storage for Mastodon and PeerTube for what a block holds and costs.