Installs Nginx from package, sets up some default configuration and defines LWRP supposed to be used inside your own cookbooks, which you use to manage your infrastructure.
Sponsored by Evil Martians
At the moment this cookbook doesn't depend on other cookbooks but it will change in the future.
The cookbook has been tested to work on Ubuntu 12.04, Ubuntu 14.04 , Ubuntu 16.04 and Debian 7
I suppose it should also work for CenOS/RHEL but no tests have been conducted yet. I have some certain plans for porting and testing this cookbook on the mentioned platforms after I finish its main funcionality.
Chef version >= 11.18.12 has to be used.
Defaults that are used to configure nginx. If you want to change one of this parameters in nginx consider using provided LWRP and definitions.
node['nginx']['directories']['conf_dir']- Base nginx config directory. Default/etc/nginx.node['nginx']['directories']['log_dir']- Directory for nginx log files. Default/var/log/nginx.node['nginx']['user']- Default user that nginx will use to run worker processes. Default:www-data.node['nginx']['worker_processes']- Number of nginx workers. Defaultcpu['total'].node['nginx']['worker_connections'] - Number of simultaneous connections that one worker can serve. Default8192`.node['nginx']['worker_rlimit_nofile']- Specifies the value for maximum file descriptors that can be opened by one worker process. Default8192.
This cookbook provides only one recipe:
This default recipe will make some basic steps:
- installs Nginx from the package that is provided by your OS's package manager ("pin" the desired version using another cookbook);
- creates all directories for configuration, directory for log files, etc;
- creates default
nginx.conffile and associated files; - configures log rotation for Nginx;
- enables and starts Nginx service;
- runs resource that removes Nginx configuration files for sites, which are not defined by this cookbook's LWRP.
This cookbook has been designed to provide LWRP for your own infrastructure recipes. First of all, we should make our infrastructure cookbook to load this one.
- Do it by adding the line
depends nginxto your cookbook's metadata.rb. - To make all default preparations for using Nginx invoke
include_recipe "nginx"inside your designated recipe. - Now feel free to use all available LWRP provided by this cookbook.
Another way to use this cookbook is just to add recipe[nginx] to your run_list before your recipe, which is resonsible for your infrastructure.
I personally prefer the first way because if you stick to it you'll eventually get complete and explicit "documentation" for your specific server installation. But in any case, you'll get Nginx installed, nginx.conf configured from the default template we provide, LWRP defined and ready to use.
If you would like to use nginx package from official nginx repo, then just add recipe[nginx::official-repo] or include_recipe 'nginx::official-repo' before nginx recipe invokation. Other wise default nginx package would be used from distro repository.
This resource manages your Nginx sites configuraions.
| Action | Description | Default |
|---|---|---|
| create | Creates site configuration file inside "sites-available" directory, but doesn't enable it. | |
| enable | Creates site configuration file inside "sites-available" directory, enables it (puts a symlink to it into "sites-enabled" directory) | Yes |
| disable | Ensures that site configuration file is disabled. | |
| delete | Disables and deletes site configuration file. |
| Attribute | Description | Default Value |
|---|---|---|
| name | Name attribute: the name of the site's configuration file. | nil |
| template | Defines what erb template file from the cookbook that invokes this resource we should use. | name.conf.erb |
| variables | Variables to be used in the template. | Hash.new |
# We want to use "example.com.conf.erb" template file, do not want to pass any variables.
nginx_site 'example.com'
# Using custom-named template file and passing some variables, which can be used inside the template.
nginx_site 'forum.example.com' do
action :enable
template 'forum-nginx.erb'
variables(
listen_ip: '10.0.0.10',
remote_ips: [ '10.0.0.2', '10.0.0.4' ]
)
end
# Making sure that old site's configuration is disabled even if somebody has enabled it by hands.
nginx_site 'old.example.com' do
action :disable
endResource is completle similar to nginx_site except it is made to manage stream section includes.
| Action | Description | Default |
|---|---|---|
| create | Creates site configuration file inside "streams-available" directory, but doesn't enable it. | |
| enable | Creates site configuration file inside "streams-available" directory, enables it (puts a symlink to it into "streams-enabled" directory) | Yes |
| disable | Ensures that site configuration file is disabled. | |
| delete | Disables and deletes site configuration file. |
| Attribute | Description | Default Value |
|---|---|---|
| name | Name attribute: the name of the stream's configuration file. | nil |
| template | Defines what erb template file from the cookbook that invokes this resource we should use. | name.conf.erb |
| variables | Variables to be used in the template. | Hash.new |
# We want to use "example.com.conf.erb" template file, do not want to pass any variables.
nginx_stream 'stream-01'
# Using custom-named template file and passing some variables, which can be used inside the template.
nginx_stream 'tcp-stream' do
action :enable
template 'nginx-stream.erb'
variables(
listen_ip: '10.0.0.10',
remote_ips: '10.0.0.2'
)
end
# Making sure that old site's configuration is disabled even if somebody has enabled it by hands.
nginx_site 'old-stream' do
action :disable
endIf you want to customize template for Nginx main configuration file, you can use this definition. It will apply passed attributes to the nginx.conf. You can only use a fixed number of core arguments that are listed below. All other Nginx arguments are meant to be set via site configurations(or conf.d directory). It can be invoked any number of times and overwrite previous changes from previous invocations so be cautious!
- accept_mutex
- accept_mutex_delay
- daemon
- debug_points
- error_log
- lock_file
- master_process
- multi_accept
- pcre_jit
- pid
- server_names_hash_bucket_size
- server_names_hash_max_size
- ssl_engine
- timer_resolution
- types_hash_bucket_size
- use
- user
- variables_hash_bucket_size
- variables_hash_max_size
- worker_connections
- worker_aio_requests
- worker_cpu_affinity
- worker_priority
- worker_processes
- worker_rlimit_core
- worker_rlimit_nofile
- worker_rlimit_sigpending
- working_directory
There are also attributes that can accept either a string or an array of strings:
nginx_mainconfig do
error_log '/var/log/nginx/new-error.log'
pid '/var/run/nginx/nginx.pid'
env [
'MALLOC_OPTIONS',
'PERL5LIB=/data/site/modules',
'OPENSSL_ALLOW_PROXY_CERTS=1'
]
debug_connection [
'127.0.0.1',
'localhost',
'192.0.2.0/24'
]
end
# Another example for env and debug_connection
nginx_mainconfig do
env 'MALLOC_OPTIONS'
debug_connection '127.0.0.1'
endAs mentioned in the previous paragraph - main nginx config file acceps only limited set of options. But we always do some tuning like enabling compression, etc. I've created two small templates for a kind of configuration I usually use. It's a bit ugly and it's atemorary solution but may become usefull if you want some standart and clean confguration fast.
Invoke each of these templates only once otherwise you'll have invalid nginx config.
Defaults to:
gzip on;
gzip_http_version 1.0;
gzip_comp_level 4;
gzip_proxied any;
gzip_types text/plain text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript application/json;
gzip_disable msie6;
gzip_vary off;
How to use:
# Use its default parameters.
nginx_site '00-gzip' do
cookbook 'nginx'
template 'gzip.conf.erb'
end
# Or you can fine tune it.
nginx_site '01-gzip' do
cookbook 'nginx'
template 'gzip.conf.erb'
variables(
enabled: true,
http_version: '1.0',
comp_version: 4,
proxied: 'any',
types: %w( text/plain text/css ),
vary: 'off'
)
endDefaults to:
sendfile on;
tcp_nopush on;
tcp_nodelay on;
server_tokens off;
reset_timedout_connection off;
keepalive_timeout 65;
How to use:
# Use its default parameters.
nginx_site '02-some-handy-defaults' do
cookbook 'nginx'
template 'some-handy-defaults.conf.erb'
end
# Or you can fine tune it.
nginx_site '03-some-handy-defaults' do
cookbook 'nginx'
template 'some-handy-defaults.conf.erb'
variables(
sendfile: 'on',
tcp_nopush: 'on',
tcp_nodelay: 'on',
server_tokens: 'off',
reset_timedout_connection: 'off',
keepalive_timeout: 65
)
endThis definition controls default log rotation settings for Nginx. Definition is used here as a wrapper because the name attibute can be omitted this way. Log rotation is enabled by default and has following configuration:
/var/log/nginx/*.log {
daily
missingok
notifempty
rotate 7
compress
create 640 root adm
delaycompress
sharedscripts
postrotate
test -f /var/run/nginx.pid && kill -USR1 "$(cat /var/run/nginx.pid)"
endscript
}
| Attribute | Description | Default Value |
|---|---|---|
| logs | Log files to be rotated. Wildcards are allowed. | /var/log/nginx/*.log |
| how_often | Defines how often we should rotate logs. Allowed values are daily, weekly, monthly. | daily |
| copytruncate | If true truncate the original log file to zero size in place after creating a copy, instead of moving the old log file and optionally creating a new one. | false |
| dateext | If true archive old versions of log files adding a daily extension like YYYYMMDD instead of simply adding a number. The extension may be configured using the dateformat option. | false |
| delaycompress | If true postpone compression of the previous log file to the next rotation cycle. This only has effect when used in combination with compress. It can be used when some program cannot be told to close its logfile and thus might continue writing to the previous log file for some time. | true |
| rotate | Log files are rotated this number of times before being removed. | 7 |
| user | Specifies the user name who will own the log file. | root |
| group | Specifies the group the log file will belong to. | adm |
| mode | Specifies the mode for the log file in octal. | 640 |
| pidfile | Path to file that contains pid nuber of Nginx master process. If copytruncate is set to false we should send USR1 signal to that Nginx process to make it reopen log files after log rotation. | /var/run/nginx.pid |
# Store rotated logs for 30 days and make them readable by everybody
nginx_logrotate do
rotate 30
mode '644'
end
# Or full tuning
nginx_logrotate do
logs ::File.join(node[:infrastucute_name][:logdir], '*.log')
how_often 'weekly'
rotate 8
copytruncate true
user 'root'
group 'adm'
mode '660'
endThis definition has no attributes or actions. Its invokation just disables the nginx_cleanup resource that is invoked by default.
The resource that is used by nginx_logrotate definition and default recipe of this cookbook and is not meant to be used inside your recipes.
It finds all enabled Nginx site's configuration symlinks (or files if somebody was was too lazy or inattentive :) ) that aren't created using nginx_site and deletes them. If you do not want this to happen use nginx_disable_cleanup definition described above.
This resource is invoked from default recipe of this cookbook and is made to be invoked only once.
Kirill Kouznetsov ([email protected])
Copyright (C) 2012-2014 Kirill Kouznetsov
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.