ptdel / tswf-api Goto Github PK

not mandatory, but could be nice. just need an spa for the endpoints, maybe pulling from /stats on nginx.

we should make the playlist an interface so that we can use queue providers. i.e. in-mem queue like we have now, or redis/memcached/etc

there are more situations now where communication between the two services is needed. I'd like to avoid the need to have the api poll the player to see if it's got a track, or the player polling the api to see if it's got a track. The new flow will be to have both the api and player subscribe to a redis or something. there will be a subscription to act as the song queue, but other subscriptions that can be used to "communicate" between the two services without directly interfacing.

should parse the link of the current song and return a json object containing metadata about the song.

• song length?
• song name?
• genre?
• idc

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

basically like a /metadata url for a track but for what's up and coming

sphinx should be added as a dependency to the project, and used to build docs during cicd (or manually).

can take the makefile approach to keep things simple, should enforce coverage.

happy to go over what needs to be documented in code, we'll need to eventually have all code covered.

doesn't have to be fancy, just some form of auth to protect /next and /skip

this is an issue for what i'm sure will be a bunch of random refactoring tasks

kind of a stupid idea, but some way to set the "mood" of the stream, so people can play similar music.

we should get rid of setting configs in a class, and instead have a class that returns a toml config as an object

I'm willing to not implement this, or make it a low priority if there is some agreement that nobody wants to listen to 10 hour YouTube videos of bullshit, or racist limericks.

I'd like this to somehow still be a democratic process, voting to ban songs and/or users. Ideally we wouldn't have this functionality... ideally. Part of this should also be some basic guards, like reasonable song lengths.

• blacklist for songs
• blacklist for users
• functionality to vote to ban a song
• functionality to vote to ban a user
• a process to appeal bans that is also democratic (everyone gets a second chance...)

I'm sure some people don't like this idea so if there is feedback leave it here and we can talk it out

api/, player/ and likely nginx/ have hardcoded urls inside of functions that should be changed to a variable loaded from configs.

add a reference to 127.0.0.1 in front of port mappings in compose files

when the player doesn't have anything in the queue and it starts to play random songs from the filesystem, the api isn't aware of this and simply reports the last song in the queue as the current track.

when you decide to do one of these, make an issue for it and check it off.

• file lifecycle for downloaded songs
• user/ip whitelist or blacklist
• song blacklist
• insert song into queue at a point in index
• fun stuff.