Heroku Blog
- News
- Last Updated: February 06, 2008
- Adam Wiggins
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 …
- News
- Last Updated: March 26, 2024
- Adam Wiggins
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.
- News
- Last Updated: January 12, 2008
- Adam Wiggins
Yesterday, DHH said:
“I’d love for Rails to be easy as pie to run in a shared hosting environment, though. I’d love for Rails to be easy as pie to run in any environment. In that ‘more people could have fun learning Rails and deploying their first hobby application’ kind of way.”
We humbly suggest that Heroku is one possible solution to the latter part of statement. Our vision for the long term is …
- News
- Last Updated: January 03, 2008
- Adam Wiggins
RSpec 1.1 is now a part of the default plugin kit for Heroku apps.
We’ve been fans of RSpec for a while now, and feel that it represents the future of TDD/BDD for the Rails world. If you’re not familiar with RSpec, read up and then give it a try.
You don’t need to install anything to use RSpec in your Heroku app, but you do need to initialize the spec/ and stories/ directories by …
- News
- Last Updated: April 04, 2024
- Adam Wiggins
Rails 1.2 is now officially deprecated for Heroku apps. Starting January 3 (that’s tomorrow), new features we are developing will not be available on apps still configured to use Rails 1.2. Then, on January 21, we will automatically upgrade any remaining 1.2 apps.
We know it’s only been a month since Rails 2 came out, so we hope this doesn’t come across as overly harsh. By taking this approach we can spend less time backporting, …
- News
- Last Updated: January 03, 2008
- Adam Wiggins
There are now two access levels for collaborators on Heroku apps:
- Full edit access, which allows access to everything: editing code, importing or exporting the database, changing the settings, etc.
- View-only access, which allows the user to view the app only. That is, they can visit the app url (myapp.heroku.com) but not any of the settings pages or the edit url (edit.myapp.heroku.com).
For example, a client who wants to use the app but neither needs …
Subscribe to the full-text feed.