Self-host TubeSync with Levelrail

Syncs chosen video channels and playlists to local storage on a schedule and keeps media library files tidy.

  • Authormeeb
  • LicenceAGPL-3.0-only
  • Memory512 MiB
  • Services1

How to self-host TubeSync

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/meeb/tubesync:v0.19.0
  2. Create the app

    One service starts in a single Compose app, with 2 named volume mounts for your data, on port 4848.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 4 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Sign in as admin with the generated password, then add a source.

TubeSync requirements

Memory
About 512 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
4848
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
AGPL-3.0-only, network copyleft (agpl) license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then TubeSync. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the TubeSync docs page.

Deploy TubeSync your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy TubeSync from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain tubesync=app.example.com.

levelrail-cli templates install tubesync --name my-tubesync

Deploy TubeSync with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/tubesync/install \
  -d '{
    "name": "my-tubesync"
  }'

TubeSync configuration

TubeSync services

ServiceImagePortsVolumes
tubesync ghcr.io/meeb/tubesync:v0.19.0 4848 config -> /configdownloads -> /downloads

TubeSync environment variables

VariableServiceValue
HTTP_PASS tubesync Generated at deploy
HTTP_USER tubesync Preset by the template
PGID tubesync Preset by the template
PUID tubesync Preset by the template
TZ tubesync Preset by the template

Ports and volumes

Ports
4848
Volumes
2 named mounts: config -> /config, downloads -> /downloads

TubeSync FAQ

How much memory does TubeSync need?

The catalog lists about 512 MiB of memory for TubeSync.

Does TubeSync run on arm64?

For TubeSync, arm64 support is not confirmed; amd64 is unknown.

What licence is TubeSync under?

TubeSync is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.

Does TubeSync need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does TubeSync use?

TubeSync listens on port 4848 inside the stack.

Where does TubeSync keep its data?

In named volumes: config mounted at /config and downloads mounted at /downloads.

Can I deploy TubeSync on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for TubeSync, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/meeb/tubesync:v0.19.0 is what you deploy there.

levelrail-cli templates install tubesync --name my-tubesync