The log level, debug is useful if you encouter any bugs The timezone of your stats, only affects read requests since data is saved with UTC time The port of the server, do not modify if you're using docker
The endpoint of the Mongo database, where mongo is the name of your service in the compose file The maximum element in the cache when importing data from an outside source, more cache means less requests to Spotify, resulting in faster imports List of comma-separated origin allowed, or nothing to allow any origin
The secret key of your Spotify application (cf Creating the Spotify Application) The public key of your Spotify application (cf Creating the Spotify Application) Note that you will still have to do the steps below. Image: yooooomi/your_spotify_client restart: always ports:ĪPI_ENDPOINT: Some ARM-based devices might have trouble with Mongo >= 5. Image: yooooomi/your_spotify_server restart: always ports:ĪPI_ENDPOINT: # This MUST be included as a valid URL in the spotify dashboard (see below) CLIENT_ENDPOINT: SPOTIFY_PUBLIC: _your_spotify_client_id_ SPOTIFY_SECRET: _your_spotify_secret_ mongo:Ĭontainer_name: mongo image: mongo:6 volumes: Installation Using docker-composeįollow the docker-compose-example.yml to host your application through docker. You need to provide an authorized redirect URI to the docker-compose file.Ī tutorial is available at the end of this readme.
You need to provide the Server environment the public AND secret key of the application (cf.You have to own a Spotify application ID that you can create through their dashboard.It's composed of a web server which polls the Spotify API every now and then and a web application on which you can explore your statistics. YourSpotify is a self-hosted application that tracks what you listen and offers you a dashboard to explore statistics about it!
0 kommentar(er)
