Fork of Passenger stack modified to support Red Hat based distributions (CentoOS, Fedora, RHE), zero to hero in under five minutes
Scripts for Sprinkle, the provisioning tool
Watch the demo screen cast of passenger-stack.
- Get a brand spanking new slice / host (Red Hat-based)
- Create yourself a user, add yourself to the /etc/sudoers file
- Set your slices url / ip address in deploy.rb (config/deploy.rb.example provided)
- Set username in config/deploy.rb if it isn't the same as your local machine (config/deploy.rb.example provided)
From your local system (from the passenger-stack directory), run:
sprinkle -c -s config/install.rb
After you've waited for everything to run, you should have a provisioned slice. Go forth and install your custom configurations, add vhosts and other VPS paraphernalia.
No superfluous configuation is included, these scripts focus purely on slice installation. Having said that passenger is configured to work with apache, your application should pretty much be a 'drop in' install.
Read these tips to get you humming
Other things you should probably consider:
- Close everything except for port 80 and 22
- Disallow password logins and use a passphrased RSA key
- Apache (Yum)
- Scripts and stylesheets are compressed using mod_deflate
- ETags are applied to static assets
- Expires headers are applied to static assets
- Ruby Enterprise (Source) [includes rubygems]
- Passenger (Rubygem)
- Memcached (Yum)
- Libmemcached (Source)
- MySQL (Yum), PostgreSQL (Yum), SQLite (Yum)
- MySQL, PostgreSQL, SQLite Ruby database drivers (Rubygem)
- Git (Source)
- Ruby
- Capistrano
- Sprinkle (github.com/crafterm/sprinkle)
- An Red Hat based VPS or EC2 instance
- Ben Schwarz, for making it very simple to customize the stack to work with Red Hat-based systems
- Marcus Crafter and other Sprinkle contributors
- Slicehost, for a free slice for testing passenger stack
- Nathan de Vries for Postgres support
- Anthony Kolber for the github pages design
- Stephen Eley for some sanity checks on git dependencies
Don't run this on a system that has already been deemed "in production", its not malicious, but there is a fair chance that you'll ass something up monumentally. You have been warned.