Alejandrothegreat

A Discord music bot with a web dashboard. Paste a Spotify link, playlist, or just search terms in Discord or the dashboard — the bot resolves the track via Spotify's API for metadata and actually plays the audio from YouTube (Spotify does not allow third-party bots to stream its audio directly, so this is the only viable approach any Spotify-integrated Discord bot uses).

Everything is configured through the web UI — no .env file to hand-edit. Log in to the dashboard with your Discord account to see every server shared by any of your bots and control playback (search, queue, skip, pause, volume, loop, shuffle) from a browser. Playback also works with !-style text commands in Discord, with the prefix configurable per server.

You can run more than one Discord bot from the same container — each with its own token, its own Discord application, and its own servers. Add, edit, enable/disable, or remove bots from /setup.html at any time; no restart required.

1. Run it

Docker Compose (recommended, also works on Unraid)

docker compose up -d --build

Locally (Node 20+)

npm install
npm start

Either way, open http://<host>:3005 (default port 3005) once it's running.

2. Set it up

On first launch the site sends you straight to the setup wizard (/setup.html) to add your first bot. You'll need:

1. A Discord application — discord.com/developers/applications → New Application. Each bot you add needs its own separate application/token - Discord bot tokens are always one-per-application.
   • Under Bot, reset the token and copy it.
   • Under Bot, enable Server Members Intent and Message Content Intent (the second one is required for !-prefix text commands).
   • Under OAuth2 → General, copy the Client ID and Client Secret.
   • Under OAuth2 → General → Redirects, add the exact redirect URI shown in the setup wizard (defaults to http://<your-host>:3005/auth/discord/callback).
2. A Spotify application (optional but recommended) — developer.spotify.com/dashboard → Create app. No redirect URI needed. Copy the Client ID and Client Secret. Without this, Spotify link/playlist resolution still works but with lower rate limits. Each bot can use a different Spotify app, or you can reuse the same one.
3. An admin password you choose yourself, only asked once for the first bot — this protects the setup page so nobody else can add, edit, or remove bots later.

Submit the form and the bot logs in immediately — no restart needed. The wizard then shows an "Add to your server" button (a ready-made Discord invite link) and a "Login with Discord" button to open the dashboard.

The first bot you add is also the one used for dashboard login (Discord OAuth needs exactly one application to authenticate against) — but once logged in, the dashboard shows servers across every bot you've added, not just that one.

To add another bot, edit an existing one's credentials, disable one temporarily, or remove one entirely, go back to /setup.html, enter your admin password, and manage the list from there.

Slash commands

Text commands

Every playback slash command above (except /dj) also works as a !-prefixed text command, e.g. !play never gonna give you up, !skip, !volume 50. The prefix defaults to ! and can be changed per server either with /dj prefix <value> or from the Server settings panel at the bottom of that server's dashboard page.

The dashboard's Server settings panel (visible to anyone with Manage Server permission) also controls who's allowed to send control commands — everyone, managers only, or a specific DJ role — the same setting slash commands, text commands, and the web dashboard all respect.

Unraid

The image is built and published automatically to GitHub Container Registry by .github/workflows/docker-publish.yml on every push to this repo: ghcr.io/turkushan490/alejandrothegreat:latest (public, no login needed to pull).

Install it on your own Unraid box right now

1. Unraid → Docker tab → Add Container.
2. Switch the template dropdown to "Enter a template URL" (top right) and paste: https://raw.githubusercontent.com/turkushan490/alejandrothegreat/master/unraid/alejandrothegreat.xml
3. It pre-fills the repository, port (3005), and appdata path (/mnt/user/appdata/alejandrothegreat). Apply.
4. Once it's running, open http://<unraid-ip>:3005/setup.html and follow the setup wizard above.

The appdata folder holds the SQLite database with your bot token, Spotify credentials, admin password, and per-server settings — back it up, and don't share it, it's more sensitive than a typical config file.

Make it show up in your own Apps search (without a public listing)

Unraid → Apps tab → Settings (gear icon) → Template repositories → add https://github.com/turkushan490/alejandrothegreat. It'll then show up when searching Apps on that box, same as any other installed app — useful while iterating before (or instead of) a public listing.

Getting it listed for everyone in Community Applications

The repo side is fully prepped and confirmed against a real, currently listed CA template (ibracorp/unraid-templates) to make sure the fields line up:

• unraid/alejandrothegreat.xml — the app template, has both Support and Project links (CA removes templates missing both)
• ca_profile.xml — the required maintainer/developer profile at the repo root
• unraid/icon.png — listing icon
• The image is public on GHCR and confirmed to pull anonymously

What's left needs to happen under your Unraid.net account, since the submission portal is account-authenticated and I don't have (and shouldn't have) your login:

1. Go to ca.unraid.net/submit and log in with your Unraid.net account.
2. Point it at this repository: https://github.com/turkushan490/alejandrothegreat
3. It runs a live scan (parses the template, validates ca_profile.xml, checks for duplicate listings) and shows a preview — fix anything it flags.
4. Submit. A support thread on the Unraid forums isn't strictly required (CA only requires a Support or Project link, and we have both), but it's worth creating one so people have somewhere to ask you questions — happy to draft that post text if/when you want it.

This step publishes the app to Unraid's whole userbase and is worth doing once you've actually run it for a while with real credentials, not necessarily on day one.

Known limitations (v1)

• Sessions are stored in memory — restarting the container logs everyone out of the dashboard (the admin password and bot credentials themselves persist fine, since those live in the database).
• YouTube audio is streamed via yt-dlp (the most reliable extractor), which auto-updates itself on container startup. If playback ever stops working after a YouTube change, restarting the container pulls the latest yt-dlp and usually fixes it. The startup logs print the resolved ffmpeg, opus, and yt-dlp versions so you can confirm the audio pipeline is healthy.
• Docker images are only tested for linux/amd64 (standard Unraid hardware).