-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
No. First visit is local administrator setup. Discord is a toggle in Admin → Discord. Local username and password always work.
When Discord sign-in is on, the first Discord user (if there is not already an administrator) is granted Administrator and their snowflake is stored in the database. You can still create administrators under Admin → Users.
Discord User Settings → Advanced → Developer Mode. Right-click the user, server, or role → Copy ID.
An administrator may have enabled a server and/or role whitelist under Admin → Discord. You must be in that server and, if the role toggle is on, have that role. Existing accounts are not blocked.
- Redirect URL must match exactly:
{SD_PUBLIC_URL}/api/v1/auth/discord/callback(no trailing slash on the public URL). -
SD_PUBLIC_URLmust be the URL you type in the browser (scheme, host, port). - Behind HTTPS or a reverse proxy, set
SD_COOKIE_SECURE=trueandSD_TRUSTED_PROXIESto the proxy CIDR.
export SD_IMAGE=ghcr.io/skila1/sounddock:latestThe package must be public, or you must docker login ghcr.io.
cd ~/sounddock
docker compose pull
docker compose up -dOr sudo sounddock update. Profiles are in .env as COMPOSE_PROFILES.
The data folder next to docker-compose.yml (for example ~/sounddock/data) and the Postgres volume. uninstall without --purge keeps them.
Create extra administrators under Admin → Users. The first Discord user is only auto-admin when no administrator exists yet.
Remote Import is for direct media file URLs. Spotify, YouTube, and similar playlist or page links go under Connected Services / playlist import. SoundDock does not download those providers' audio.
No. It searches and streams your library.
Yes. See Integration. Start at /api/docs on your instance.
-
/healthzand/readyzon the server -
sudo sounddock doctorchecks Docker andhttp://127.0.0.1:8080/healthz
cd ~/sounddock
docker compose down # keep data
docker compose down -v && sudo rm -rf ~/sounddock