v2.0.0-beta3

• Moved some sane default node attributes into roles so you don't need to specify them in your node attributes.
• Added support for Phusion Passenger with the rails_passenger role.
• Updated Vagrantfile to use Chef Omnibus so you can test the recipes in the same way that you install them on your own server.
• Minor fixes to configuration templates and updated cookbooks.

v2.0.0-beta2

• Simplified the variables you need to configure for your node because we moved some sane defaults into the Chef role definitions.
• Added support for Phusion Passenger with the rails_passenger role.
• Updated Vagrantfile to use Chef Omnibus so you can test the recipes in the same way that you install them on your own server.
• Cleaned up template Unicorn configuration.
• Updated rbenv cookbook.

v2.0.0-alpha

• Important: To use this new version you will need to update your node configuration file so this breaks backwards compatibility.
• Use the rbenv community cookbook instead of the rbenv-chef via submodule.
• Added support for installing SSL certificates for your Rails app (#29)
• Default node[:nginx][:server_tokens] to off in sample_host.json to not expose version information about nginx to potential attackers.
• Improve stability for starting the Rails application processes with bluepill.
• Add support for the intercity gem for super easy application setup and capistrano deployment: https://github.com/intercity/intercity-gem
• Updated all cookbooks to latest versions.
• We now have a guides website: http://www.intercityup.com/guides
• Bind MySQL address to 127.0.0.1 in sample node config.
• Added Ubuntu 12.04 LTS default sudo parameters to sample node config.
• Updated rbenv section in sample node config.

User per app

This is the collection of Chef recipes we use to manage our Ruby on Rails servers at Firmhouse.

Changelog

• Added specifying a user per deployment. This is the user the application will run as and that you configure in your Capistrano configuration to deploy the application.

Features

• Prepares an Ubuntu 12.04 LTS server for running a full Rails stack.
• Multiple apps on one server.
• Scaringly simple setup by running only two commands.
• Deploy with Capistrano
• Nginx as web server
• Unicorn with zero-downtime/rolling restarts
• Bluepill for Rails process and memory monitoring
• (Percona) MySQL Server for databases
• Manages and generates your database.yml

Getting Started

Short version:

Download the tarball or clone the repository.

bundle
bundle exec knife solo prepare user@host

Edit nodes/host.json

bundle exec knife solo cook user@host

See the README for an extended guide on getting started.

Troubleshooting and getting help

We've tested with a bunch of VPS vendors and setups ranging from clean Ubuntu installs to pre-configured vendor images and have solved all problems we recognized so far.

If you run into problems, please open a GitHub issue so we can take a look at your situation.

The Hello World release

This is the first public release of the collection of Chef recipes we use to manage our Ruby on Rails servers at Firmhouse. We've been using these in production for over a few months now so it's time to push out 1.0.0. Yay!

Features

• Prepares an Ubuntu 12.04 LTS server for running a full Rails stack.
• Multiple apps on one server.
• Scaringly simple setup by running only two commands.
• Deploy with Capistrano
• Nginx as web server
• Unicorn with zero-downtime/rolling restarts
• Bluepill for Rails process and memory monitoring
• (Percona) MySQL Server for databases
• Manages and generates your database.yml

Getting Started

Short version:

Download the tarball or clone the repository.

bundle
bundle exec knife solo prepare user@host

Edit nodes/host.json

bundle exec knife solo cook user@host

See the README for an extended guide on getting started.

Troubleshooting and getting help

We've tested with a bunch of VPS vendors and setups ranging from clean Ubuntu installs to pre-configured vendor images and have solved all problems we recognized so far.

If you run into problems, please open a GitHub issue so we can take a look at your situation.