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

Adam Wiggins

Heroku Staff

Why NoSQL Matters “NoSQL” is a label which encompasses a wave of innovation now happening in the database space. The NoSQL movement has sparked a whirlwind of discussion, debate, and excitement in the technical community. Why is NoSQL generating so much buzz? What does it mean for you, the application developer? And what place does NoSQL have for apps running on the Heroku platform? SQL (the language) and SQL RDBMS implementations (MySQL, PostgreSQL, Oracle, etc) have been the one-size-fits-all solution for data persistence and retrieval for decades. The rise of the web and the LAMP stack cemented the role of…

Our goal for the Heroku platform has been to create a totally smooth and seamless experience for getting your Ruby web application online. Web apps revolve around one or more dynamic web processes: what Rubyists often call a mongrel, and what we call a dyno. When it comes to dynos, we think we’ve really nailed it, and nothing makes that more tangible than the ease of scaling your app with the dyno slider. But most serious web apps have a second aspect: one that gets less attention, but one that is often just as important as the web process. Like…

Our good friends at Shopify recently released a developer platform which makes it crazy easy to build custom functionality into an e-commerce store using a standalone Rails app. There are already some great apps available in their app store, many of which are running on Heroku. Check out the excellent getting started video by James MacAulay. It shows just how slick the Shopify API is – these guys are really taking e-commerce to the next level. (And bonus points for use of config vars to store API keys!)

Say you’re working on a [Rails app](https://www.heroku.com/ruby), and you want to publish your code on Github. Most apps have some deploy-specific private config values – for example, if you’re using the S3 storage back-end for Paperclip, and your S3 keys are saved in config/amazon_keys.yml. You certainly don’t want to push those up to Github – what to do? You could maintain a separate deploy branch, and commit your deploy config only to that. You can then work on the main branch, and rebase the deploy branch whenever you go for a deploy. That’s a bit of extra work you could…

Heroku is now sporting an updated docs layout at docs.heroku.com. These new docs should be much easier to navigate and link to. We built this as a standalone Sinatra app serving Markdown files, partially inspired by Assaf Arkin’s approach to Buildr. This makes it as snappy as staticly rendered pages, while retaining the flexibility of a dynamic app on the backend. The docs app is deployed as a regular app on Heroku (just like this blog). Nothing special-case here: we deploy with git push, just like any other Heroku user. Dogfooding is good for you. The app’s source is on…

The past eighteen months have seen an explosion of Rails-inspired Ruby web frameworks. Merb and Sinatra are the best known; plus many others such as Ramaze, Camping, and Waves. That’s why we’re so pleased to announce the ability to deploy any Rack-compatible web app to Heroku. Assuming you have a Heroku account, here’s how you can deploy a Sinatra app in about 30 seconds. Make a new directory, and inside create hello.rb: require ‘rubygems’ require ‘sinatra’ get ‘/’ do “Hello from Sinatra on Heroku!” end Then create a config.ru file in the same directory: require ‘./hello’ run Sinatra::Application Now let’s…

Application deployment is changing. In relatively short order I’ve gone from buying hardware, to monthly hosting, to metered CPU time, and from building my open-source software manually, to package managers, to fancy config tools and recipes to pre-build whole machine images. What’s next? The Old Way I can deploy Rails apps in a traditional hosting environment pretty quickly. For a small app, I might make a new unix user and database on a personal Slicehost slice and do a quick code checkout. After setting up a few permissions and twiddling my Nginx config, in a matter of fifteen minutes or…

The gem for Rails 2.2 is now installed and ready for use on Heroku. To use, change your environment.rb to read: RAILS_GEM_VERSION = ‘2.2.2’ Then run rake rails:update, and commit the changed files. Check out the Ruby Inside article for more details on what’s new.

Hoptoad (now Airbrake) is a great service by Thoughtbot for collecting exceptions. Like exception_notifier, but without clogging your inbox, and much prettier. Using Hoptoad with Heroku is a cinch. First, sign up for a free Hoptoad account. Now install their notifier plugin. If you’re working locally and deploying to Heroku with Git, install with script/plugin: script/plugin install git://github.com/thoughtbot/hoptoad_notifier.git Or if you’re using the Heroku web editor, open the vendor folder and click Gems & Plugins, then enter the plugin URL in the “Install from URL” box at the bottom. Next, create a new file config/initializers/hoptoad.rb containing: HoptoadNotifier.configure do |config| config.api_key…

The Heroku API gets a major update today; you can now view and manage all of your application’s settings straight from the command line. New in this version: Manage sharing (add/remove/list collaborators) Manage multiple ssh keys for your user (add/remove/list keys) Update settings (public true/false, mode production/development) Rename an app Run rake tasks remotely A taste of the new command-line goodness: adam@kvasir:~$ heroku create gagetron Created http://gagetron.heroku.com/ | git@heroku.com:gagetron.git adam@kvasir:~$ heroku info gagetron === gagetron Web URL: http://gagetron.heroku.com/ Git Repo: git@heroku.com:gagetron.git Mode: development Public: false Collaborators: adam@example.com (edit) adam@kvasir:~$ heroku sharing gagetron –add joe@example.com joe@example.com added as a view-only collaborator…

Subscribe to the full-text RSS feed for Adam Wiggins.