Simply put, spockify is an application that provides a shared queue through Spotify Connect. Anyone with local access to the service can add to and view this shared queue simply by visting the web application (though we can imagine implementing some basic authentication down the road).
Written and tested with Python 3.7 (as of this writing of course). No guarantees of anything less than the latest version of Python is a good rule of thumb here.
We also make use of flask and spotipy to make all the glue coding easier (thanks for that).
Register a Spotify application under your account. See Spotify's guide here. Note that this may end up being out of date at some point.
You'll need to set the environment variables that spotipy uses (or alternatively just use the equivalent command line arguments, see --help for more):
SPOCKIFY_CLIENT_IDSPOCKIFY_CLIENT_SECRETSPOCKIFY_REDIRECT_URI
The first two are self explanatory (hopefully), and the second can just be set to http://localhost/ -- though note that you need to authorize this redirect uri in the settings of your registered Spotify application.
Once you have those sorted out and you'll installed all the dependencies, just run python3 app.py {username}. Your browser will open asking you to authenticate and authorize with Spotify. When Spotify redirects you, just grab the url from your browser and paste it into the prompt that is waiting. Then, you should be good to go. Visit localhost:5000 in your browser.
This is a super hacked up prototype at this point so don't expect anything fancy.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
GPLv3, see LICENSE