Queens-Hacks / qcumber-api

transforms qcumber data repo into something blah
1 stars 3 forks source link

Hosting #3

Open uniphil opened 10 years ago

uniphil commented 10 years ago

This is a bit down the road, like when we actually have something to host, but...

Requirements

I'm down to chip in or cover a DigitalOcean one. I've been using them a bunch over the last months, seem pretty solid.

I lean toward that over something like Heroku because I think we've got enough dev/ops power on this team that the control would be nice. Thinking long-term though, maybe keeping up qcumber in the years to come will be more approachable if it's just a heroku dyno? I'm sure qcumber gets enough traffic that dynos idling down wouldn't be an issue..

Graham42 commented 10 years ago

I'd also be down to chip in if it's needed. Have no opinion on what we should use because I haven't any experience with them.

mystor commented 10 years ago

I like the idea of putting it on a heroku dyno because it would make it really easy to set up, however we would probably not be able to put the api and frontend on the same server, meaning that it may be a bit more pricey than the other options.

The other problem comes with database choice. Heroku comes with (IIRC) a small free postgres database, but has no free/cheap option for a mongo database without going to a cloud mongo provider, which will probably be another $15-20/month.

DO sounds like a good option as long as we keep puppet-like scripts set up to configure it and document how to maintain it.

I think Qcumber.ca is on WebFaction... http://www.whois.com/whois/qcumber.ca, so that is another option.