Search overlay panel for performing site-wide searches
Salesforce (Heroku) Named a Leader. Learn More!

Heroku Blog

We are happy this morning to announce we’ve raised a $3 million round of funding, from Redpoint Ventures and some other great investors.

Adam, Orion, and I started Heroku with the goal of making software development much easier and more accessible. We’ve got big plans – what we’ve done so far is really just the first step. There is so much we’ve been dying to do, but we just haven’t had the capacity.

This investment will allow us to beef up our current offerings, expand into other parts of the development process, and build out…

Heroku now has an API (accessible from the command line, a Ruby library, or REST calls), revision control on all apps with Git, and remote access to the Git repository.

The combination of these new features means that you can now work on your apps using the local tools you love – like TextMate, vi, or emacs – and still get the benefit of zero-configuration deployment to Heroku.

How does it work? Grab the Heroku gem with “gem install heroku”. A sample work session looks like this:

heroku clone myapp
cd myapp
ruby script/server
…edit locally…
git add .
git…

Heroku now has a mailing list on Google Groups. Stop by and introduce yourself, but first read the welcome post .


If you’re curious about our vision for Heroku, check out the latest episode of the Ruby on Rails Podcast . We spoke with Geoffrey Grosenbach about our plans for Heroku, the Rails ecosystem, and some good old fashioned economics.

Last night we noticed a flood of .jp email addresses appearing on the waiting list – several hundred over the course of just a few hours. Turns out someone posted a comprehensive and flattering review of Heroku in Japanese   (translation) . I just couldn’t resist using the opportunity to post this image:

Actually, it’s not just Japan: the international response to Heroku has astonished us. Denmark, New Zealand, France, Russia, Brazil – over half of our users are from outside the US. We chalk this up more to the universal appeal of Ruby and Rails…

Backstory: A Fiery Debate

Writing a user model and the standard login authentication code seems like busywork to a lot of coders. In fact, many people expected a next-generation app framework such as Rails to handle this for you. After all, Django does . Initially the login engine for Rails seemed to fill this slot, but following a fair amount of controversy over best practices, the login engine was killed by its creator.

With our BDfL having forever cursed prebuilt login systems , the Rails community mostly stopped trying to make them. …

Subscribe to the full-text feed.