Ask HN: Am I crazy to port my Rails app to PHP?
I've recently been working on a small, "hobby" web app - http://yoyocase.net. It's been a chance for me to scratch an itch (I want to show off my collection) as well as to learn Rails.
Finding hosting for my app has been challenging, though. I don't plan on monetizing this, so I really can't justify "expensive" web hosting. Nor do I want to go with a VPS - I don't want to play sysadmin in my spare time.
So, I've also been porting my code to PHP (not raw; CodeIgniter!), and plan to put it on my shared hosting account. Am I shooting myself in the foot?
Alternatively, do any of you know where I could find relatively cheap "shared" Rails hosting - a place where I wouldn't have to setup my own virtual server(s), keep all the software/packages up to date, etc.?
21 comments
[ 1.7 ms ] story [ 55.5 ms ] threadhttp://blog.heroku.com/archives/2010/1/21/pricing_changes_pa...
Give it a try!
I jumped on the Rails band wagon early and loved all the syntatic sugar that comes from Ruby, and I'd never really developed with an MVC pattern.
Like you, I gradually realized I was spending more time as a sysadmin or bashing my clients' commodity hosting into submission than actually building sites. I felt like I was cheating when I finally went back to PHP (CodeIgniter, also).
It wasn't til I rsync'd the PHP site I was working on to the prod server and saw it just work that I started feeling a bit better. Since then, I've been totally happy using simple but solid PHP frameworks.
So, I think you're on the right track. Admittedly, I'm a little out of date on the state of Rails deployment. But if you're productive in PHP, go for it.
But honestly, it's whatever language works best for you. If you've got a good framework in front of it that's helping to keep you from making dumb mistakes, then that's all that really matters.
Second, there is surely alot of rails-hosters out there, keep looking if you want to build your app with pure ror.But the beatuy of php is what you already have seen; it just works!
That said, I have experienced and heard that the time made up by using Rails/Ruby, is much less than the time it takes to customize a Rails app to get it to do what you want. Especially when there's a lot of customization. What I like about PHP and frameworks like CodeIgnitor, is that customization is dead easy. You only write code for what you want to achieve, you don't need to work around the framework's preset functionality.
Short answer, it depends. A lot of customization, use PHP, something that fits with Ruby/Rails, use that.
Also, if you use git, it's really easy to deploy an app by just pushing up to Heroku.
Now that I have small children (3 and 2 yr/olds) it makes me want to take up the hobby again to show them the fun in it. So, think about ways that your site could grow into something that you hadn't originally thought of. Example: if you had instructions/videos demonstrating yo-yo tricks. A searchable, fun way for people to show off their hobby.
So, if you had the desire to monetize this one day, you may actually have some interest from people. This is just to say that maybe you shouldn't keep a tight lid on your ideas.
Good luck!
I have thought some about montization (mostly in the context of "If this thing grows, how will I pay for hosting beyond my own personal/hobby threshold?"), and have two ideas:
1) fremium - subscriptions for the "serious" collector (more data fields, etc.)
2) ads from yoyo manufacturers/organizations (there aren't many, hence I don't think AdSense would really draw much revenue; plus, I actually have a few contacts at Duncan)
If I had to pick one of those, I'd rather pick #2 - I can't imagine this site, as I currently plan to build it, would add enough value to justify subscriptions.
Anyway, if you want to pick it up again, I recommend: - http://www.theyo.com/yoyo/ and http://www.theyostore.com/ - http://www.yo-yoing.com/news/ - http://www.yoyonation.com - http://yoyowiki.org