ROR on cloud or so one click install (tar or zip your application and upload just like you do Java base application using Tomcat)

Yes they have database import /export little different but they have to compare to so many db format to take care.

I had Flex & ROR running on local PC and looking at ISP to deploy on web (thinking of paying some $$ to host) but heroku solved the problem and now I can test and deploy or go public at my convenience.

But hey, these guys rock.

THEY HAVE MADE WEB APPLICATION DEVELOPMENT n DEPLOYMENT ON RAILS AS EASY AS BLOGGING OR PHOTO SHARING!!!

This is why I like it
* Zero Setup. Why muck around when you really want to get stuck into coding
* You don’t need to remember to restart for config changes – it does it automatically (how many times have I forgotten to do that and wondered why my changes aren’t working)
* You don’t need to remember to migrate (did I mention I’m a bit forgetful on that front)
* I can get to my app from any machine – saves having to carry the laptop home
* You can have more than one person working on the app at once, see changes in real time without any special set up.
* I don’t have to leave the browser at all – none of this browser/textmate/MySQL Query Browser switching.

There’ll always be a place for doings things locally and deploying yourself with your own special setup but its great to have alternatives.

Good luck to Adam, James and Orion. I’m a fan.

Shrikant

Overall, GREAT news.

Let’s be honest. Rails deployment sucks.

PS: I love how everyone says you don’t need a virtual/dedicated server. You don’t, but the second you have a problem or it is running slow, go into #rubyonrails and ask. You will get five people telling you, “Just buy a virtual server.”

Jamie, I’m a Rails developer by day, and I’ve never had to learn any of these, and I haven’t even heard of some of them. I’m not sure what you’re saying here, but it’s not an argument against Rails or for PHP. You can put PHP behind apache or nginx, too.

That said, I’m not going to say “Heroku = fail” yet, because moving something from 2 steps (rails foo && foo/script/server) to 1 step might just be enough to bring more people on board. I am skeptical, though. Hosting isn’t trivial, but any solution that starts out “OK, give up your editor and terminal and version control and offline editing” seems pretty fishy for anything beyond the 15-minute blog demo.

Although I’m still deciding between RoR and going back to PHP via the Zend_Framework. Zend_Framework looks smooth. Ruby language wise seems to have some powerful stuff you just don’t have in PHP though. This is my conundrum.

http://switchpipe.org/

BTW, try deploying a large PHP app sometime. Rails’ framework and tool stack doesn’t look so bad…

Secondly, I’ve semi-solved the deployment issues regarding caretaking Mongrels and all that nonsense. It’s called SwitchPipe. It’s one app. It works, it monitors, it maintains, and you don’t have to get involved with port numbers, clusters, or any such nonsense.

Heroku = Fail.

My question for Heroku is how they scale the database? This is a big problem with Amazon Web Service until as of late when they introduced SimpleDB which is still in private beta currently.