Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

Music backend as separate process #121

Open
Ovyerus opened this issue Nov 4, 2017 · 2 comments
Open

Music backend as separate process #121

Ovyerus opened this issue Nov 4, 2017 · 2 comments
Assignees
Milestone

Comments

@Ovyerus
Copy link
Contributor

Ovyerus commented Nov 4, 2017

(title sucks I know)

This will be a separate process that acts like a server (using Nodes HTTP lib) and will handle all the fetching for music information and streams, and might even be the general music manager, which caches data and plays them when supposed to (similar to LavaLink I guess).

@Ovyerus Ovyerus added this to the 1.0.0 milestone Nov 4, 2017
@Ovyerus Ovyerus self-assigned this Nov 4, 2017
@sr229
Copy link
Contributor

sr229 commented Nov 4, 2017

@Ovyerus the problem is, how do we execute the seperate process, like the Chatbot server? We relied so much in the init process of the bot

@Ovyerus
Copy link
Contributor Author

Ovyerus commented Nov 4, 2017

Either on bot init (when the music events get loaded) or having it start separately, like as an extra thing specified in the pm2.json, because you can specify multiple programs to run from a process file for pm2.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants