(i.e. stick with Plain Old EC2, VPS, etc.) • Not everyone is willing to endure a Capistrano based workflow (RVM?, passenger?, rubygems?, bundler?, before/ after_hooks...) => not a reliable nor straightforward process. • Willing to better integrate your app deployment process with infrastructure automation tools (Puppet/Chef): package {"my-rails-app": ensure => installed } (better use your native OS’s package manager to deploy your app)
of a Rails3 app. Self-contained app + app server (thin) • Uses system ruby, so that you get the security updates • Bundles everything else inside the package (avoids library dependency hell with other apps/system gems), even bundler.
/etc/my-rails-app/*.yml • Change how the app server is launched by adding options to /etc/default/my-rails-app • Log files will be stored in /var/log/my-rails-app/ • Db files (if any) will be stored in /var/db/my-rails-app/
files: pkgr --uri https://github.com/edavis10/redmine --ref master --bump 1.4.1 \ -c https://raw.github.com/crohr/pkgr/master/examples/redmine/configuration.yml \ -c https://raw.github.com/crohr/pkgr/master/examples/redmine/database.yml \ -c https://raw.github.com/crohr/pkgr/master/examples/redmine/pkgr.yml \ --host debian-build => this example packages the latest Redmine version (instead of the offical package, still based on Rails2.3).