-
Notifications
You must be signed in to change notification settings - Fork 2
Hosting: Pros and Cons
Where do we host this thing?!
😃 Can control multiple music player servers anywhere on the net (ie. a Pi running libspotify) from a single collaboration room. Requires decoupling the server app from the music player app (good idea anyway).
😡 Associated cloud hosting costs
😡 Client app is available on internet, anyone can sign-up so would need a way to grant access to rooms/groups of rooms
😡 Likely overly complex for an MVP
😃 Simpler implementation ideal for MVP
😃 No significant running costs (just base costs: Spotify Premium, initial hardware, ⚡ electricity ⚡ 😺)
😃 Runs on local network, client app is accessible via internal IP address. No worries about granting access. If you have access to the local network, you're free to sign up via your favourite OAuth provider.
😕 Can Raspberry Pi hardware cope with serving the client app (http routes + socket connections) as well as running the music player? We'd unlikely to have more people than would fit in a room use it and I reckon the specs of the Pi 2 Model B means it's worth a shot
😡 Can't have people collaborate from multiple locations within the same room, but considering our core use-case, that's okay for MVP :)
Stick it all on a Pi 2 Model B — that'd be a good start.