Deployment options

Setlistto is self-hosted software. Each installation uses the operator's own hosting environment, persistent storage, Spotify Developer app, and backup process. Most bands should start with the local Docker install, then move to a public host only if they need always-on access outside one machine.

Option 1

Local Docker

Run a one-container install with persistent state mounted outside the container.

Option 2

Cloud self-hosting

Deploy the Rails app to a VPS or supported app host, usually backed by managed Postgres.

Option 3

Managed install

Get help choosing a supported target, configuring the instance, and connecting Spotify.

Blah, blah, blah…
sync my songs already!
Or, Let's Dig In

Local Docker quick start

The installer pulls the public Docker image, starts a one-container app with a persistent Docker volume, chooses an available local port, saves that port for future updates, and prints the URL to open.

curl -fsSL https://setlistto.com/scripts/docker-install.sh | sh

Setlistto will prepare its data files and send you to the first-run setup screen. To inspect the installer first, open https://setlistto.com/scripts/docker-install.sh in your browser.

Stay Current

Update the local Docker app

The updater pulls the latest public image, keeps the same local port and data volume, asks before stopping a running container, and replaces it.

curl -fsSL https://setlistto.com/scripts/docker-update.sh | sh

What you need before setup

  • Docker installed on the machine that will run Setlistto.
  • The public setlistto/setlistto Docker image.
  • A Spotify Developer account and a Spotify app for this instance.
  • The public or local URL where you will open Setlistto.

First-run Spotify setup

  1. Create a Spotify app and copy its Client ID.
  2. Open Setlistto and confirm the Setlistto URL.
  3. Copy the redirect URI shown by Setlistto into your Spotify app.
  4. In the Spotify app, open Settings -> User Management and add the Spotify account that will connect to Setlistto.
  5. Save the Client ID in Setlistto.
  6. Connect Spotify with the account that should own the instance.

Setlistto uses Authorization Code with PKCE, so it does not need a Spotify Client Secret. Spotify may return HTTP 403 for development-mode apps when the connected account has not been added in User Management.

Want the full guide?

The customer install guide covers update steps, backups, and troubleshooting notes for the public image.

Ask a Question

Prefer setup help?

Managed install and priority support are available if you want help choosing a host, configuring Spotify, or getting through the first sync.

View Help Options