search

atleastimtrying / rubber_duck

Rubber ducking as a service.
MIT License
110 stars 6 forks source link

arrange hosting #6

Closed atleastimtrying closed 10 years ago

atleastimtrying commented 10 years ago

github pages? heroku?

undecided commented 10 years ago

Github pages only works statically, no? I would be happy to spin up a DigitalOcean server to host it, otherwise Heroku should handle it so long as the traffic isn't too high for too long... gets a bit expensive otherwise.

atleastimtrying commented 10 years ago

well does it need a server side component? there's no need for serious persistence! Also flat files would be far more scalable!

undecided commented 10 years ago

True. Happy to let Github handle the load, depending on our final answer to https://github.com/atleastimtrying/rubber_duck/issues/3

Another possibility (and I only mention it because it came up last NRUG) is Google App Engine. JRuby & Sinatra should work, full might of google to handle our traffic. Not sure what their pricing structure is like.

atleastimtrying commented 10 years ago

I would suggest we work on a front end approach first (surprise surprise) and go with github for #3 then if we get far along enough we think about using apis and requesting anonymous caching to help others rubber duck, then we move onto digital ocean/whatever.