-
-
Notifications
You must be signed in to change notification settings - Fork 180
Open
Description
Not sure if Spotify have changed something yet again, but I cannot for love nor money get my deployment stable since the changes and I've been down for over 3 months. Documentation doesn't seem to have been updated to reflect the changes either...
Anyone able to see where I'm going wrong?
Compose:
services:
your_spotify_server:
container_name: your_spotify_server
image: yooooomi/your_spotify_server
restart: unless-stopped
links:
- mongo_your_spotify_server
depends_on:
- mongo_your_spotify_server
environment:
API_ENDPOINT: http://10.0.5.69:8080
CLIENT_ENDPOINT: http://10.0.5.69:3000
SPOTIFY_PUBLIC: xyz123
SPOTIFY_SECRET: xyz123
TIMEZONE: Europe/London
CORS: i-want-a-security-vulnerability-and-want-to-allow-all-origins
MONGO_ENDPOINT: mongodb://mongo_your_spotify_server:27017/your_spotify
ports:
- "8080:8080"
mongo_your_spotify_server:
container_name: mongo_your_spotify_server
image: mongo:6
restart: unless-stopped
volumes:
- /containers/v-cont-01/data/your_spotify_server/data:/data/db
your_spotify_server_client:
container_name: your_spotify_server_client
image: yooooomi/your_spotify_client
restart: unless-stopped
environment:
API_ENDPOINT: http://10.0.5.69:8080
ports:
- "3000:3000"
Spotify URI:
I have tried every combination of (standalone or at the same time]
[http or https]://[127.0.0.1 or localhost or 10.0.5.69]:[80 or 8080 or 3000 or 443 or 4423]/oauth/spotify/callback (and /api/oauth... despite not using the LSIO image)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels