Ask HN: Hosting a Ruby on Rails app
3 comments
I'd go with Heroku to start. Its free to start, but does jump quickly to $36/month, and you can decide at that time where you want to take it - more Heroku, VPS, dedicated etc.
I haven't used Heroku, but then I haven't deployed a 'small' rails app since before Heroku started.
Edit: Also, make sure you're using Ruby 1.9.x - this alone will give you a bunch of extra performance to allow you to run more users on the same configuration at the low end
I haven't used Heroku, but then I haven't deployed a 'small' rails app since before Heroku started.
Edit: Also, make sure you're using Ruby 1.9.x - this alone will give you a bunch of extra performance to allow you to run more users on the same configuration at the low end
Long term, what are the options for hosting once an app grows? At some point, does it become a requirement to bring your server in-house and do your own hosting and server maintenance?
The hardest part of moving to a new service is moving the data over. For a small app, you can do the 'stop everything; copy data; restart everything on new location' thing in a short amount of time without annoying too many people.
If you need to start an app on a cheap or free service, and then it succeeds, you should try to look 2 steps ahead for your move to take into account the data moving problem. The good news with Heroku is that you can just keep adding capacity while you work this out.
There are hosters out there - Engine Yard is well known in the Rails world - who can help you do this if you don't want to run stuff yourself. I've used a company called Bitpusher in the past as well.
At some point though, you will want to bring this in-house as it grows. If only for the cost aspect. Owning your own hardware and employing your own ops people will be cheaper than paying someone else. This is probably a long way into the future for this specific case.
If you need to start an app on a cheap or free service, and then it succeeds, you should try to look 2 steps ahead for your move to take into account the data moving problem. The good news with Heroku is that you can just keep adding capacity while you work this out.
There are hosters out there - Engine Yard is well known in the Rails world - who can help you do this if you don't want to run stuff yourself. I've used a company called Bitpusher in the past as well.
At some point though, you will want to bring this in-house as it grows. If only for the cost aspect. Owning your own hardware and employing your own ops people will be cheaper than paying someone else. This is probably a long way into the future for this specific case.
Thanks, this has been extremely helpful :-)
Find some place that offers Passenger Phusion. Makes hosting a breeze.
Also, if hosting/scaling becomes an issue, you might look at running your app under JRuby and hosting it using a Java app server. There's some overhead in learning about configuration, and such, but it can solve certain problems.
I've been using Railsplayground as a staging server, and while it works OK (though there's near zero load on it) I had stuff break because they decided to upgrade from Ruby 1.8.6 to 1.8.7. Plus, there's no `screen`, for example, which makes things a little harder than they need be.
Not being root means you have to live with other people's decisions.
Also, if hosting/scaling becomes an issue, you might look at running your app under JRuby and hosting it using a Java app server. There's some overhead in learning about configuration, and such, but it can solve certain problems.
I've been using Railsplayground as a staging server, and while it works OK (though there's near zero load on it) I had stuff break because they decided to upgrade from Ruby 1.8.6 to 1.8.7. Plus, there's no `screen`, for example, which makes things a little harder than they need be.
Not being root means you have to live with other people's decisions.
dream host is good for about 10 visitors, after that you'll have to go to a VPS. I like rimuhosting- outstanding service for about $30/month. You get access to a virtual server, not a web interface, so you get a root account with a terminal.
Has anybody had any regrets after going this route?
I've read that Rails doesn't perform so well in these types of environments. Is it something to worry about when I'm still small or only if my app becomes very popular?
I saw HostingRails.com had a special offer for their Stacked plan. Has anybody used them and can provide feedback?