Configuration

Spotify Developer Setup

Before using Clispot, you must create a Spotify Developer application and configure your credentials.

Step 1: Create a Spotify Application

1. Go to the Spotify Developer Dashboard and log in.
2. Click on “Create an app”.
3. Give your application a name and description.
4. Find the “Redirect URIs” section and add the following URI:

   http://127.0.0.1:9292/callback

5. Save your changes.
6. Now, view your application’s settings and find your Client ID and Client Secret.

Step 2: Configure Environment Variables

Linux / macOS

Add the following lines to your shell’s configuration file (e.g., .bashrc, .zshrc, or .profile):

export SPOTIFY_CLIENT_ID="<your-client-id>"
export SPOTIFY_CLIENT_SECRET="<your-client-secret>"

After adding these lines, reload your shell configuration:

source ~/.bashrc  # or ~/.zshrc

Windows

PowerShell

To set them for the current session:

$env:SPOTIFY_CLIENT_ID="<your-client-id>"
$env:SPOTIFY_CLIENT_SECRET="<your-client-secret>"

To make them permanent (User level):

[System.Environment]::SetEnvironmentVariable('SPOTIFY_CLIENT_ID', '<your-client-id>', 'User')
[System.Environment]::SetEnvironmentVariable('SPOTIFY_CLIENT_SECRET', '<your-client-secret>', 'User')

Command Prompt (cmd)

To set them for the current session:

set SPOTIFY_CLIENT_ID=<your-client-id>
set SPOTIFY_CLIENT_SECRET=<your-client-secret>

To make them permanent:

setx SPOTIFY_CLIENT_ID "<your-client-id>"
setx SPOTIFY_CLIENT_SECRET "<your-client-secret>"

Note: Without these credentials, Clispot will not be able to authenticate with Spotify.

Application Configuration

Clispot supports a persistent configuration file located at ~/.config/clispot/config.json (or $XDG_CONFIG_HOME/clispot/config.json). This allows you to set defaults for various options without passing flags every time.

Configuration File Structure

Here is an example of a complete config.json file:

{
  "debug-dir": "/home/user/.local/state/clispot/logs",
  "cache-dir": "/home/user/.cache/clispot",
  "disable-cache": false,
  "yt-dlp-args": {
    "cookies-from-browser": "firefox",
    "cookies": "/path/to/cookies.txt"
  }
}

Configuration Precedence

Clispot applies configuration in the following order of precedence (highest to lowest):

1. Command Line Flags: Options passed directly to the clispot command (e.g., --debug-dir, --cache-dir, --headless).
2. Configuration File: Settings defined in ~/.config/clispot/config.json (Linux), %AppData%\clispot\config.json (Windows), or ~/Library/Application Support/clispot/config.json (macOS).
3. Defaults: Hardcoded application defaults.

This means if you have headless-mode: true in your config file but run clispot --headless=false, the application will start in normal mode.

Authentication

On first run, clispot will:

1. Start a local web server on port 9292
2. Open your default browser to Spotify’s authorization page
3. Ask you to authorize the application
4. Save the authentication token to your configuration directory (e.g., ~/.config/clispot/token.json or %AppData%\clispot\token.json)

The token is automatically refreshed when needed. You only need to authenticate once (unless you revoke it).

File Locations

• Config: (Respects XDG_CONFIG_HOME on Linux/macOS, defaults to ~/.config on Linux, %AppData% on Windows, ~/Library/Application Support on macOS)
  • clispot/token.json - Stores Spotify authentication token
  • clispot/config.json - Application settings (optional)
• Cache: (Respects XDG_CACHE_HOME on Linux, defaults to ~/.cache on Linux, %LocalAppData% on Windows, ~/Library/Caches on macOS)
  • clispot/yt-audio/ - Cached audio files from YouTube
• Debug logs (State): (Respects XDG_STATE_HOME on Linux, defaults to ~/.local/state on Linux, %AppData% on Windows, ~/Library/State on macOS)
  • clispot/logs/ytstderr.log - YouTube downloader error logs
  • clispot/logs/ffstderr.log - FFmpeg conversion error logs
  • Log location depends on the -d flag:
    • If -d <path> is specified: logs are saved in that directory
    • If not specified: logs are saved in ~/.local/state/clispot/logs (Linux), ~/Library/State/clispot/logs (macOS), or %AppData%\clispot\logs (Windows).

These logs can be useful for troubleshooting playback issues and reporting bugs.