Kitchen to setup an Ubuntu Server ready to roll with Nginx, PostgreSQL, Redis Server and Rails.
- Ubuntu 12.04+
To cook with this kitchen you must follow four easy steps.
We create our deploy user in deploy server adding our SSH keys:
sudo adduser deploy --disabled-password
# Add your SSH keys to deploy authorized_keys
sudo mkdir /home/deploy/.ssh/
sudo vim /home/deploy/.ssh/authorized_keys
sudo chown deploy:deploy -R /home/deploy/git clone git://github.com/acidlabs/chef-rails.git chef
cd chef
bundle install
bundle exec librarian-chef installWe need to copy chef-solo to any server we’re going to setup. For each server, execute
bundle exec knife solo prepare [user]@[host] -p [port]where
- user is a user in the server with sudo and an authorized key.
- host is the ip or host of the server.
- port is the port in which ssh is listening on the server. Defaul port: 22.
If you take a look at the nodes folder, you’re going to see files called [host].json, corresponding to the hosts or ips of the servers we previously prepared, plus a file called localhost.json.example which is, as its name suggests, and example.
The specs for each server needs to be defined in those files, and the structure is exactly the same as in the example.
For the very same reason, we’re going to exaplain the example for you to ride on your own pony later on.
{
// This is the list of the recipes that are going to be cooked.
"run_list": [
"recipe[apt]",
"recipe[sudo]",
"recipe[build-essential]",
"recipe[ohai]",
"recipe[runit]",
"recipe[git]",
"recipe[postgresql]",
"recipe[postgresql::contrib]",
"recipe[postgresql::server]",
"recipe[nginx]",
"recipe[nginx::apps]",
"recipe[redis::install_from_package]",
"recipe[redis::client]",
"recipe[monit]",
"recipe[monit::ssh]",
"recipe[monit::nginx]",
"recipe[monit::postgresql]",
"recipe[monit::redis-server]",
"recipe[rvm::user]",
"recipe[chef-rails]"
],
"automatic": {
"ipaddress": "<host_ip>"
},
// You must define who’s going to be the user(s) you’re going to use for deploy.
"authorization": {
"sudo": {
"groups" : ["deploy","vagrant"],
"users" : ["deploy","vagrant"],
"passwordless": true
}
},
// You must define the password for postgres user.
// Leave config block commented untill next cook.
"postgresql": {
"contrib": {
"extensions": ["pg_stat_statements"]
},
// "config": {
// "shared_buffers": "125MB",
// "shared_preload_libraries": "pg_stat_statements"
// },
"password" : {
"postgres": "<postgres_user_password>"
}
},
// You must specify the ubuntu distribution by it’s name to configure the proper version
// of nginx, otherwise it’s going to fail.
"nginx": {
"user" : "deploy",
"distribution" : "trusty",
"components" : ["main"],
"worker_rlimit_nofile": 30000,
// Here you should define all the apps you want nginx to serve for you in the server.
"apps": {
// Example for an application served by Unicorn server
"example.com": {
"listen" : [80],
"server_name": "example.com www.example.com",
"public_path": "/home/deploy/production.example.com/current/public",
"upstreams" : [
{
"name" : "example.com",
"servers" : [
"unix:/home/deploy/production.example.com/shared/pids/example.com.sock max_fails=3 fail_timeout=1s"
]
}
],
"locations": [
{
"path": "/",
"directives": [
"proxy_set_header X-Forwarded-Proto $scheme;",
"proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;",
"proxy_set_header X-Real-IP $remote_addr;",
"proxy_set_header Host $host;",
"proxy_redirect off;",
"proxy_http_version 1.1;",
"proxy_set_header Connection '';",
"proxy_pass http://example.com;"
]
},
{
"path": "~ ^/(assets|fonts|system)/|favicon.ico|robots.txt",
"directives": [
"gzip_static on;",
"expires max;",
"add_header Cache-Control public;"
]
}
]
},
// Example for an application served by Thin server
"example2.com": {
"listen" : [80],
"server_name": "example2.com www.example2.com",
"public_path": "/home/deploy/production.example2.com/current/public",
"upstreams" : [
{
"name" : "example2.com",
"servers" : [
"0.0.0.0:3000 max_fails=3 fail_timeout=1s",
"0.0.0.0:3001 max_fails=3 fail_timeout=1s"
]
}
],
"locations": [
{
"path": "/",
"directives": [
"proxy_set_header X-Forwarded-Proto $scheme;",
"proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;",
"proxy_set_header X-Real-IP $remote_addr;",
"proxy_set_header Host $host;",
"proxy_redirect off;",
"proxy_http_version 1.1;",
"proxy_set_header Connection '';",
"proxy_pass http://example2.com;"
]
},
{
"path": "~ ^/(assets|fonts|system)/|favicon.ico|robots.txt",
"directives": [
"gzip_static on;",
"expires max;",
"add_header Cache-Control public;"
]
}
]
}
}
},
// The ruby version you’re going to use and rvm user.
"rvm" : {
"user_installs": [
{
"user" : "deploy",
"default_ruby" : "ruby-2.1.2"
}
]
},
// Monit configuration. Sets email, check period and delay since monit service start
"monit" : {
"notify_email" : "email@example.com",
"poll_period" : "60",
"poll_start_delay" : "120"
},
// Finally, declare all the system packages required by the services and gems you’re using in your apps.
// To give you an example: If you’re using paperclip, the native extensions compilation will fail unless you have installed imagemagick declared below.
"chef-rails": {
"packages": ["imagemagick", "nodejs-dev"]
}
}We’re now ready to cook. For each server you want to setup, execute
bundle exec knife solo cook [user]@[host] -p [port]following the same criteria we defined in step 2.
Remember to clean your kitchen after cook
bundle exec knife solo clean [user]@[host] -p [port]sudo -u postgres psql
CREATE USER deploy SUPERUSER ENCRYPTED PASSWORD '<deploy_user_password>';
\qHere are some issues with current cookbooks recipes, we have to solve them, so it's kind a TODO list:
ssh [user]@[host] -p [port]
sudo pg_createcluster 9.3 main --start
exit
bundle exec knife solo cook [user]@[host] -p [port]Uncomment the following block in PostgreSQL configuration:
// "config": {
// "shared_buffers": "125MB", // 1/4 of total memory is recommended
// "shared_preload_libraries": "pg_stat_statements"
// },Then, cook again.