soundtrack
soundtrack copied to clipboard
Hosting
I'd like to get a dedicated box for soundtrack.io. I'll be doing this regardless, but I'd like to see what resources people have.
Requirements mainly are Linux. Ideally, the hosting would be outside of the US.
I could put it on a VM on my rack server, but it's inside the US :(
Been using digitalocean a lot lately, cheap and they have servers in AMS.
On Tue, Jan 28, 2014 at 12:21 PM, Nate [email protected] wrote:
I could put it on a VM on my rack server, but it's inside the US :(
Reply to this email directly or view it on GitHubhttps://github.com/martindale/soundtrack.io/issues/87#issuecomment-33507418 .
I also have rack space in San Francisco.
omg DigitalOcean is fantastic. great recommend overra
I've got a referral code that will make me $10 once you spend $10 in service. https://www.digitalocean.com/?refcode=de8382fc5f6a
One nice thing about digitalocean is that you pay by hour, $0.007/hr for the $5/mo package. I had a pretty good experience with a weekend project that generated a lot of traffic around the end of December. It was really easy to scale up once I made an image of the main server.
Edit: accidentally a word
On Tue, Jan 28, 2014 at 12:35 PM, Nate [email protected] wrote:
omg DigitalOcean is fantastic. great recommend overra
Reply to this email directly or view it on GitHubhttps://github.com/martindale/soundtrack.io/issues/87#issuecomment-33508840 .
@martindale not outside the US, but Open Shift (@openshift) by RH is great. Easy scaling and deployment - and "small gears" are free.
Best of all, the entire platform is free software.
Awesome! Thanks, @gordonwritescode! I'll take a look.
I think the action plan is something like this:
- [ ] move hosting outside of US.
- [ ] build prototype federated hosting platform (as a framework?)
- [ ] integrate into soundtrack.io
- [ ] make accessible via CJDNS
Anyone have thoughts on 2? Would we need to switch from username/password auth to keypair authentication? Would each "deploy" be its own room?