fix(lavalink): drop spotify-tokener, lavasrc uses client credentials

- spotify URL resolution was broken (500 NPE): preferPartnerApi +
  customTokenEndpoint depended on dead spotify-tokener (-32000)
- remove tokener service from compose, remove dead SPOTIFY_* env from
  bot container (bot code never used them)
- spotify metadata now resolves via standard client credentials,
  playback is mirrored to SoundCloud via scsearch providers (ISRC/QUERY)
This commit is contained in:
loki5512344 2026-08-30 00:29:13 +02:00
parent 5e83356016
commit 4cbbb36159
Signed by: boba
GPG key ID: 253067914055423B
3 changed files with 57 additions and 16 deletions

View file

@ -3,8 +3,6 @@ services:
image: ghcr.io/lavalink-devs/lavalink:4-alpine
container_name: loki-lavalink
restart: unless-stopped
depends_on:
- spotify-tokener
ports:
- "127.0.0.1:2333:2333"
volumes:
@ -22,16 +20,6 @@ services:
retries: 3
start_period: 20s
spotify-tokener:
image: ghcr.io/topi314/spotify-tokener:master
container_name: spotify-tokener
restart: unless-stopped
environment:
- SPOTIFY_TOKENER_ADDR=0.0.0.0:8086
- SPOTIFY_TOKENER_LOG_LEVEL=INFO
networks:
- default
bot:
build: .
container_name: loki-bot
@ -54,8 +42,6 @@ services:
LAVALINK_HOST: lavalink
LAVALINK_PORT: "2333"
LAVALINK_PASSWORD: Hch4HiVCxkKs9JPiSnrt4Q
SPOTIFY_CLIENT_ID: ${SPOTIFY_CLIENT_ID}
SPOTIFY_CLIENT_SECRET: ${SPOTIFY_CLIENT_SECRET}
R34_API_KEY: ${R34_API_KEY}
R34_USER_ID: ${R34_USER_ID}
DEEPSEEK_API_KEY: ${DEEPSEEK_API_KEY}