capistrano-resque_monit 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: aee995561346647eec7ac2c16742b4090722454c
+  data.tar.gz: 182950bdc7039715846ad45c76eec6e00a54b5e5
+SHA512:
+  metadata.gz: 6afb8e1be581124abe2101161c221f95406ac13eed56504ad30886fec040fd36396120d34b57344af1e037e5c94fe51cf4c5e9e4dd3b51bfa6aca11716a6f33f
+  data.tar.gz: 9745f079e2aa734ead85beba8aebd3a82b4019cf4e55ef93d90ddc1bccc2eca718e1ab59ff7cf437bf59a6a4ef8008e97ab45a3df264ae440a70a0b411528b44

data/.gitignore

@@ -0,0 +1,35 @@
+*.gem
+*.rbc
+/.config
+/coverage/
+/InstalledFiles
+/pkg/
+/spec/reports/
+/test/tmp/
+/test/version_tmp/
+/tmp/
+
+## Specific to RubyMotion:
+.dat*
+.repl_history
+build/
+
+## Documentation cache and generated files:
+/.yardoc/
+/_yardoc/
+/doc/
+/rdoc/
+
+## Environment normalisation:
+/.bundle/
+/vendor/bundle
+/lib/bundler/man/
+
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+Gemfile.lock
+.ruby-version
+.ruby-gemset
+
+# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
+.rvmrc

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in capinstrano-resque_monit.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2015 Keylime Toolbox
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,46 @@
+# capistrano-resque_monit
+
+A set of Capistrano scripts for configuring resque workers to be monitored by monit
+
+## Installation
+
+### Note
+This gem requires Capistrano to deploy using `sudo`. This is because scripts are generated and copied
+to `/usr/local/bin`, `/etc/init.d/` and `/etc/monit.d`.
+
+Add this line to your application's Gemfile:
+
+    gem 'capistrano-resque_monit'
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install capistrano-resque_monit
+
+## Usage
+
+Add to your `Capfile`:
+
+    require 'capistrano/resque_monit/tasks' 
+
+Set resque prefix for app in `deploy.rb`
+
+    set :resque_prefix 'APP_NAME'
+
+Setup values for monit in `deploy.rb`
+
+    set :monit_user
+    set :monit_password
+    set :monit_url
+    set :monit_email
+
+## Contributing
+
+1. Fork it ( https://github.com/keylimetoolbox/capistrano-resque_monit/fork )
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create a new Pull Request

data/Rakefile

@@ -0,0 +1,2 @@
+require "bundler/gem_tasks"
+

data/capistrano-resque_monit.gemspec

@@ -0,0 +1,25 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'capistrano/resque_monit/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "capistrano-resque_monit"
+  spec.version       = Capistrano::ResqueMonit::VERSION
+  spec.authors       = ["Gino Clement", "Jeremy Wadsack"]
+  spec.email         = ["ginoclement@gmail.com", "jeremy@keylimetoolbox.com"]
+  spec.summary       = "Deploying Resque and Monit using Capistrano."
+  spec.description   = "A set of Capistrano scripts for configuring resque workers to be monitored by monit"
+  spec.homepage      = "https://github.com/keylimetoolbox/capinstrano-resque_monit"
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files -z`.split("\x0")
+  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
+  spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
+  spec.require_paths = ["lib"]
+
+  spec.add_dependency "capistrano", "~> 3.0"
+
+  spec.add_development_dependency "bundler", "~> 1.6"
+  spec.add_development_dependency "rake", "~> 10.0"
+end

data/lib/capistrano/resque_monit/monit.rb

@@ -0,0 +1,70 @@
+after 'monit:config', 'monit:restart'
+
+namespace :monit do
+
+  task :config, :except => { :no_release => true } do
+    run 'sudo chkconfig monit on'
+  end
+
+  task :status do
+    run 'sudo monit status'
+  end
+
+  task :log do
+    run 'sudo tail -f /var/log/monit'
+  end
+
+  task :start do
+    run 'sudo monit start all'
+  end
+
+  task :stop do
+    run 'sudo monit stop all'
+  end
+
+  task :restart, :except => { :no_release => true } do
+    run 'sudo monit reload'
+    run 'sudo monit summary all'
+  end
+end
+
+def sed_initd(file, role)
+  sed_template "templates/etc/init.d/#{file}", {
+      CURRENT: current_path,
+      PIDFILE: "tmp/pids/#{file}.pid",
+      RAILSENV: rails_env,
+      GEMHOME: "#{rvm_path}/gems/#{rvm_ruby_string}",
+  }, '/etc/init.d/#{file}'
+end
+
+def sed_monitd(file, role)
+  sed_template "templates/etc/monit.d/#{file}", {
+      HOST: server_name,
+      EMAIL: monit_email
+  }, '/etc/monit.d/#{file}'
+end
+
+def sed_monitrc
+  sed_template "templates/monitrc", {
+    USER: monit_user,
+    PASSWORD: monit_password,
+    URL: monit_url
+  }, '/etc/monitrc'
+  run 'sudo chmod 600 /etc/monitrc'
+end
+
+def sed_bin(file, role)
+  resque_config = YAML.load_file('config/resque_monit.yml')
+  (host, port) = resque_config[rails_env].split ':'
+  sed_template "templates/usr/local/bin/#{file}", {
+      RESQUE_HOST: host,
+      RESQUE_PORT: port
+  }, '/usr/local/bin/#{file}'
+  run "sudo chmod 755 /usr/local/bin/#{file}"
+end
+
+def sed_template file, values, dest
+  cmds = values.map { |k, v| "-e 's/%#{k}%/#{v.gsub(%r(/), '\\/')}/g'" }.join ' '
+  run "cd #{deploy_to}/current && sudo sed #{cmds} #{file} > #{dest}"
+end
+

data/lib/capistrano/resque_monit/resque.rb

@@ -0,0 +1,58 @@
+# Requires that a :worker role is defined in your configuration
+
+# TODO: Update template paths
+
+after 'deploy', 'resque_monit:restart'
+after 'deploy:migrations', 'resque_monit:restart'
+
+namespace :resque_monit do
+
+  task :restart, roles: :worker, :except => { :no_release => true } do
+    run 'sudo monit reload'
+    sleep 2
+    run "sudo monit -g #{resque_prefix}_resque_workers restart"
+    run "sudo monit -g #{resque_prefix}_resque_workers summary"
+  end
+
+end
+
+def resque_template(filename, values)
+  template = File.open(File.join('templates', filename)).read
+  template.gsub(/#\{([^}]+)\}/) { |m| values[$1.to_sym]}
+end
+
+
+def resque_worker_monitd(file, options = {})
+  file = "#{file}_#{resque_prefix}"
+
+  mem = options[:totalmem] || '675'
+
+  depends = []
+  depends << 'redis'
+  depends << options[:depends]
+  depends.flatten!
+  depends.compact!
+  depends = depends.empty? ? '' : "depends on #{depends.join(', ')}"
+
+  script = resque_template('resque_monitd', depends: depends, file: file, current_path: current_path, mem: mem, resque_prefix: resque_prefix)
+
+  put script, "#{current_path}/tmp/#{file}", :mode => 0644
+  run "sudo mv #{current_path}/tmp/#{file} /etc/monit.d/#{file}"
+  run "sudo chown root:root /etc/monit.d/#{file}"
+end
+
+
+def resque_worker_initd(worker, options = {})
+
+  queue = options[:queue] || worker
+
+  file = "resque_worker"
+  file += "_#{resque_prefix}"
+  file += "_#{worker}"
+
+  script = resque_template('resque_initd', rvm_path: rvm_path, rvm_ruby_string: rvm_ruby_string, current_path: current_path, rails_env: rails_env, queue: queue, file: file)
+
+  put script, "#{current_path}/tmp/#{file}", :mode => 0755
+  run "sudo mv #{current_path}/tmp/#{file} /etc/init.d/#{file}"
+  run "sudo chown root:root /etc/init.d/#{file}"
+end

data/lib/capistrano/resque_monit/tasks.rb

@@ -0,0 +1,25 @@
+load 'capistrano/resque_monit/monit'
+load 'capistrano/resque_monit/resque'
+
+# TODO: Update templates path to Gem root path
+
+namespace :monit do
+  desc 'Set up base files'
+  task :setup do
+    sed_monitrc
+    run "cd #{deploy_to}/current && sudo cp templates/*.conf /etc"
+  end
+
+  desc 'Set up init.d and monit.d files for monit'
+  task :config_app, :roles => :app, :except => { :no_release => true } do
+    sed_monitd 'nginx', :app
+  end
+end
+
+namespace :resque_monit do
+  desc 'Set up init.d and monit.d files for all resque_monit workers'
+  task :config_worker, :roles => :worker, :except => { :no_release => true } do
+    sed_initd 'resque_scheduler', :worker
+    sed_bin 'redis-check-queue', :worker
+  end
+end

data/lib/capistrano/resque_monit/version.rb

@@ -0,0 +1,5 @@
+module Capistrano
+  module ResqueMonit
+    VERSION = "0.0.1"
+  end
+end

data/lib/capistrano/resque_monit.rb

@@ -0,0 +1,6 @@
+require "capistrano/resque_monit/version"
+
+module Capistrano
+  module ResqueMonit
+  end
+end

data/templates/etc/init.d/monit

@@ -0,0 +1,86 @@
+#!/bin/bash
+#
+# Init file for Monit system monitor
+# Written by Stewart Adam <s.adam@diffingo.com>
+# based on script by Dag Wieers <dag@wieers.com>.
+#
+# chkconfig: 2345 98 02
+# description: Utility for monitoring services on a Unix system
+#
+# processname: monit
+# config: /etc/monit.conf
+# pidfile: /var/run/monit
+# Short-Description: Monit is a system monitor
+
+# Source function library.
+. /etc/init.d/functions
+
+### Default variables
+CONFIG="/etc/monitrc"
+prog="monit"
+bin="/usr/local/bin/$prog"
+
+# Check if requirements are met
+[ -x $bin ] || exit 1
+[ -r "$CONFIG" ] || exit 1
+
+RETVAL=0
+
+start() {
+	echo -n $"Starting $prog: "
+	$bin -Ic "$CONFIG" &
+	RETVAL=$?
+	echo
+	[ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog
+	return $RETVAL
+}
+
+stop() {
+	echo -n $"Shutting down $prog: "
+	killproc $prog
+	RETVAL=$?
+	echo
+	[ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/$prog
+	return $RETVAL
+}
+
+restart() {
+	stop
+	start
+}
+
+reload() {
+	echo -n $"Reloading $prog: "
+	$bin -Ic "$CONFIG" reload
+	RETVAL=$?
+	echo
+	return $RETVAL
+}
+
+case "$1" in
+  start)
+	start
+	;;
+  stop)
+	stop
+	;;
+  restart)
+	restart
+	;;
+  reload)
+	reload
+	;;
+  condrestart)
+	[ -e /var/lock/subsys/$prog ] && restart
+	RETVAL=$?
+	;;
+  status)
+	status $prog
+	RETVAL=$?
+	;;
+  *)
+	echo $"Usage: $0 {start|stop|restart|reload|condrestart|status}"
+	RETVAL=1
+esac
+
+exit $RETVAL

data/templates/etc/init.d/resque_scheduler

@@ -0,0 +1,24 @@
+#! /bin/sh
+
+cd_path="%CURRENT%"
+export_gem_home="export GEM_HOME=%GEMHOME%"
+
+case "$1" in
+  start)
+        echo -n "Starting resque_scheduler: "
+                su - deploy -c "cd $cd_path && $export_gem_home && bundle exec rake RAILS_ENV=%RAILSENV% PIDFILE=%PIDFILE% resque:scheduler >> log/resque_scheduler.log 2>&1 &"
+        echo "OK."
+        ;;
+  stop)
+        echo -n "Stopping resque_scheduler: "
+                su - deploy -c "kill -QUIT `cat $cd_path/%PIDFILE%` && rm -f $cd_path/%PIDFILE% && exit 0"
+        echo "done."
+        ;;
+      *)
+            N=/etc/init.d/resque_scheduler
+            echo "Usage: $N {start|stop}" >&2
+            exit 1
+            ;;
+esac
+
+exit 0

data/templates/etc/monit.d/alert

@@ -0,0 +1 @@
+set alert %EMAIL% but not on { action }

data/templates/etc/monit.d/logging

@@ -0,0 +1 @@
+set logfile /var/log/monit

data/templates/etc/monit.d/nginx

@@ -0,0 +1,4 @@
+check host nginx address %HOST%
+  if failed host %HOST% port 80 then alert
+  start = "/sbin/service nginx start" with timeout 60 seconds
+  stop = "/sbin/service nginx stop"

data/templates/etc/monit.d/redis

@@ -0,0 +1,3 @@
+check process redis with pidfile "/var/run/redis/redis.pid"
+  start = "/etc/init.d/redis start" with timeout 60 seconds
+  stop = "/etc/init.d/redis stop"

data/templates/monitrc

@@ -0,0 +1,17 @@
+# Below is our very simple Monit config file -- for documentation and
+# Examples, check the Monit website!
+
+set daemon 60
+set logfile syslog facility log_daemon
+set mail-format { subject: monit alert [$HOST]: $EVENT $SERVICE }
+include /etc/monit.d/*
+set httpd port 2812 and
+  allow %USER%:%PASSWORD%
+
+set eventqueue basedir /var/monit slots 1000
+
+# Specify the URL for posting events to M/Monit. The auth. part of
+# the URL, that is, monit:monit, specify a username and password
+# registered in M/Monit. If you change the password for the monit
+# user in M/Monit it must be changed here as well.
+set mmonit %URL%

data/templates/redis.conf

@@ -0,0 +1,540 @@
+# Redis configuration file example
+
+# Note on units: when memory size is needed, it is possible to specify
+# it in the usual form of 1k 5GB 4M and so forth:
+#
+# 1k => 1000 bytes
+# 1kb => 1024 bytes
+# 1m => 1000000 bytes
+# 1mb => 1024*1024 bytes
+# 1g => 1000000000 bytes
+# 1gb => 1024*1024*1024 bytes
+#
+# units are case insensitive so 1GB 1Gb 1gB are all the same.
+
+# By default Redis does not run as a daemon. Use 'yes' if you need it.
+# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
+daemonize yes
+
+# When running daemonized, Redis writes a pid file in /var/run/redis.pid by
+# default. You can specify a custom pid file location here.
+pidfile /var/run/redis/redis.pid
+
+# Accept connections on the specified port, default is 6379.
+# If port 0 is specified Redis will not listen on a TCP socket.
+port 6379
+
+# If you want you can bind a single interface, if the bind option is not
+# specified all the interfaces will listen for incoming connections.
+#
+#bind 127.0.0.1
+
+# Specify the path for the unix socket that will be used to listen for
+# incoming connections. There is no default, so Redis will not listen
+# on a unix socket when not specified.
+#
+# unixsocket /tmp/redis.sock
+# unixsocketperm 755
+
+# Close the connection after a client is idle for N seconds (0 to disable)
+timeout 300
+
+# Set server verbosity to 'debug'
+# it can be one of:
+# debug (a lot of information, useful for development/testing)
+# verbose (many rarely useful info, but not a mess like the debug level)
+# notice (moderately verbose, what you want in production probably)
+# warning (only very important / critical messages are logged)
+loglevel notice
+
+# Specify the log file name. Also 'stdout' can be used to force
+# Redis to log on the standard output. Note that if you use standard
+# output for logging but daemonize, logs will be sent to /dev/null
+logfile /var/log/redis/redis.log
+
+# To enable logging to the system logger, just set 'syslog-enabled' to yes,
+# and optionally update the other syslog parameters to suit your needs.
+# syslog-enabled no
+
+# Specify the syslog identity.
+# syslog-ident redis
+
+# Specify the syslog facility.  Must be USER or between LOCAL0-LOCAL7.
+# syslog-facility local0
+
+# Set the number of databases. The default database is DB 0, you can select
+# a different one on a per-connection basis using SELECT <dbid> where
+# dbid is a number between 0 and 'databases'-1
+databases 16
+
+################################ SNAPSHOTTING  #################################
+#
+# Save the DB on disk:
+#
+#   save <seconds> <changes>
+#
+#   Will save the DB if both the given number of seconds and the given
+#   number of write operations against the DB occurred.
+#
+#   In the example below the behaviour will be to save:
+#   after 900 sec (15 min) if at least 1 key changed
+#   after 300 sec (5 min) if at least 10 keys changed
+#   after 60 sec if at least 10000 keys changed
+#
+#   Note: you can disable saving at all commenting all the "save" lines.
+#
+#   It is also possible to remove all the previously configured save
+#   points by adding a save directive with a single empty string argument
+#   like in the following example:
+#
+#   save ""
+
+save 900 1
+save 300 10
+save 60 10000
+
+# By default Redis will stop accepting writes if RDB snapshots are enabled
+# (at least one save point) and the latest background save failed.
+# This will make the user aware (in an hard way) that data is not persisting
+# on disk properly, otherwise chances are that no one will notice and some
+# distater will happen.
+#
+# If the background saving process will start working again Redis will
+# automatically allow writes again.
+#
+# However if you have setup your proper monitoring of the Redis server
+# and persistence, you may want to disable this feature so that Redis will
+# continue to work as usually even if there are problems with disk,
+# permissions, and so forth.
+stop-writes-on-bgsave-error yes
+
+# Compress string objects using LZF when dump .rdb databases?
+# For default that's set to 'yes' as it's almost always a win.
+# If you want to save some CPU in the saving child set it to 'no' but
+# the dataset will likely be bigger if you have compressible values or keys.
+rdbcompression yes
+
+# Since verison 5 of RDB a CRC64 checksum is placed at the end of the file.
+# This makes the format more resistant to corruption but there is a performance
+# hit to pay (around 10%) when saving and loading RDB files, so you can disable it
+# for maximum performances.
+#
+# RDB files created with checksum disabled have a checksum of zero that will
+# tell the loading code to skip the check.
+rdbchecksum yes
+
+# The filename where to dump the DB
+dbfilename dump.rdb
+
+# The working directory.
+#
+# The DB will be written inside this directory, with the filename specified
+# above using the 'dbfilename' configuration directive.
+#
+# Also the Append Only File will be created inside this directory.
+#
+# Note that you must specify a directory here, not a file name.
+dir /var/lib/redis/
+
+################################# REPLICATION #################################
+
+# Master-Slave replication. Use slaveof to make a Redis instance a copy of
+# another Redis server. Note that the configuration is local to the slave
+# so for example it is possible to configure the slave to save the DB with a
+# different interval, or to listen to another port, and so on.
+#
+# slaveof <masterip> <masterport>
+
+# If the master is password protected (using the "requirepass" configuration
+# directive below) it is possible to tell the slave to authenticate before
+# starting the replication synchronization process, otherwise the master will
+# refuse the slave request.
+#
+# masterauth <master-password>
+
+# When a slave lost the connection with the master, or when the replication
+# is still in progress, the slave can act in two different ways:
+#
+# 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
+#    still reply to client requests, possibly with out of date data, or the
+#    data set may just be empty if this is the first synchronization.
+#
+# 2) if slave-serve-stale data is set to 'no' the slave will reply with
+#    an error "SYNC with master in progress" to all the kind of commands
+#    but to INFO and SLAVEOF.
+#
+slave-serve-stale-data yes
+
+# You can configure a slave instance to accept writes or not. Writing against
+# a slave instance may be useful to store some ephemeral data (because data
+# written on a slave will be easily deleted after resync with the master) but
+# may also cause problems if clients are writing to it because of a
+# misconfiguration.
+#
+# Since Redis 2.6 by default slaves are read-only.
+#
+# Note: read only slaves are not designed to be exposed to untrusted clients
+# on the internet. It's just a protection layer against misuse of the instance.
+# Still a read only slave exports by default all the administrative commands
+# such as CONFIG, DEBUG, and so forth. To a limited extend you can improve
+# security of read only slaves using 'rename-command' to shadow all the
+# administrative / dangerous commands.
+slave-read-only yes
+
+# Slaves send PINGs to server in a predefined interval. It's possible to change
+# this interval with the repl_ping_slave_period option. The default value is 10
+# seconds.
+#
+# repl-ping-slave-period 10
+
+# The following option sets a timeout for both Bulk transfer I/O timeout and
+# master data or ping response timeout. The default value is 60 seconds.
+#
+# It is important to make sure that this value is greater than the value
+# specified for repl-ping-slave-period otherwise a timeout will be detected
+# every time there is low traffic between the master and the slave.
+#
+# repl-timeout 60
+
+# The slave priority is an integer number published by Redis in the INFO output.
+# It is used by Redis Sentinel in order to select a slave to promote into a
+# master if the master is no longer working correctly.
+#
+# A slave with a low priority number is considered better for promotion, so
+# for instance if there are three slaves with priority 10, 100, 25 Sentinel will
+# pick the one wtih priority 10, that is the lowest.
+#
+# However a special priority of 0 marks the slave as not able to perform the
+# role of master, so a slave with priority of 0 will never be selected by
+# Redis Sentinel for promotion.
+#
+# By default the priority is 100.
+slave-priority 100
+
+################################## SECURITY ###################################
+
+# Require clients to issue AUTH <PASSWORD> before processing any other
+# commands.  This might be useful in environments in which you do not trust
+# others with access to the host running redis-server.
+#
+# This should stay commented out for backward compatibility and because most
+# people do not need auth (e.g. they run their own servers).
+#
+# Warning: since Redis is pretty fast an outside user can try up to
+# 150k passwords per second against a good box. This means that you should
+# use a very strong password otherwise it will be very easy to break.
+#
+# requirepass foobared
+
+# Command renaming.
+#
+# It is possible to change the name of dangerous commands in a shared
+# environment. For instance the CONFIG command may be renamed into something
+# of hard to guess so that it will be still available for internal-use
+# tools but not available for general clients.
+#
+# Example:
+#
+# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
+#
+# It is also possible to completely kill a command renaming it into
+# an empty string:
+#
+# rename-command CONFIG ""
+
+################################### LIMITS ####################################
+
+# Set the max number of connected clients at the same time. By default
+# this limit is set to 10000 clients, however if the Redis server is not
+# able ot configure the process file limit to allow for the specified limit
+# the max number of allowed clients is set to the current file limit
+# minus 32 (as Redis reserves a few file descriptors for internal uses).
+#
+# Once the limit is reached Redis will close all the new connections sending
+# an error 'max number of clients reached'.
+#
+# maxclients 10000
+
+# Don't use more memory than the specified amount of bytes.
+# When the memory limit is reached Redis will try to remove keys
+# accordingly to the eviction policy selected (see maxmemmory-policy).
+#
+# If Redis can't remove keys according to the policy, or if the policy is
+# set to 'noeviction', Redis will start to reply with errors to commands
+# that would use more memory, like SET, LPUSH, and so on, and will continue
+# to reply to read-only commands like GET.
+#
+# This option is usually useful when using Redis as an LRU cache, or to set
+# an hard memory limit for an instance (using the 'noeviction' policy).
+#
+# WARNING: If you have slaves attached to an instance with maxmemory on,
+# the size of the output buffers needed to feed the slaves are subtracted
+# from the used memory count, so that network problems / resyncs will
+# not trigger a loop where keys are evicted, and in turn the output
+# buffer of slaves is full with DELs of keys evicted triggering the deletion
+# of more keys, and so forth until the database is completely emptied.
+#
+# In short... if you have slaves attached it is suggested that you set a lower
+# limit for maxmemory so that there is some free RAM on the system for slave
+# output buffers (but this is not needed if the policy is 'noeviction').
+#
+# maxmemory <bytes>
+
+# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
+# is reached? You can select among five behavior:
+#
+# volatile-lru -> remove the key with an expire set using an LRU algorithm
+# allkeys-lru -> remove any key accordingly to the LRU algorithm
+# volatile-random -> remove a random key with an expire set
+# allkeys-random -> remove a random key, any key
+# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
+# noeviction -> don't expire at all, just return an error on write operations
+#
+# Note: with all the kind of policies, Redis will return an error on write
+#       operations, when there are not suitable keys for eviction.
+#
+#       At the date of writing this commands are: set setnx setex append
+#       incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
+#       sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
+#       zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
+#       getset mset msetnx exec sort
+#
+# The default is:
+#
+# maxmemory-policy volatile-lru
+
+# LRU and minimal TTL algorithms are not precise algorithms but approximated
+# algorithms (in order to save memory), so you can select as well the sample
+# size to check. For instance for default Redis will check three keys and
+# pick the one that was used less recently, you can change the sample size
+# using the following configuration directive.
+#
+# maxmemory-samples 3
+
+############################## APPEND ONLY MODE ###############################
+
+# By default Redis asynchronously dumps the dataset on disk. This mode is
+# good enough in many applications, but an issue with the Redis process or
+# a power outage may result into a few minutes of writes lost (depending on
+# the configured save points).
+#
+# The Append Only File is an alternative persistence mode that provides
+# much better durability. For instance using the default data fsync policy
+# (see later in the config file) Redis can lose just one second of writes in a
+# dramatic event like a server power outage, or a single write if something
+# wrong with the Redis process itself happens, but the operating system is
+# still running correctly.
+#
+# AOF and RDB persistence can be enabled at the same time without problems.
+# If the AOF is enabled on startup Redis will load the AOF, that is the file
+# with the better durability guarantees.
+#
+# Please check http://redis.io/topics/persistence for more information.
+
+appendonly no
+
+# The name of the append only file (default: "appendonly.aof")
+# appendfilename appendonly.aof
+
+# The fsync() call tells the Operating System to actually write data on disk
+# instead to wait for more data in the output buffer. Some OS will really flush
+# data on disk, some other OS will just try to do it ASAP.
+#
+# Redis supports three different modes:
+#
+# no: don't fsync, just let the OS flush the data when it wants. Faster.
+# always: fsync after every write to the append only log . Slow, Safest.
+# everysec: fsync only one time every second. Compromise.
+#
+# The default is "everysec" that's usually the right compromise between
+# speed and data safety. It's up to you to understand if you can relax this to
+# "no" that will let the operating system flush the output buffer when
+# it wants, for better performances (but if you can live with the idea of
+# some data loss consider the default persistence mode that's snapshotting),
+# or on the contrary, use "always" that's very slow but a bit safer than
+# everysec.
+#
+# More details please check the following article:
+# http://antirez.com/post/redis-persistence-demystified.html
+#
+# If unsure, use "everysec".
+
+# appendfsync always
+appendfsync everysec
+# appendfsync no
+
+# When the AOF fsync policy is set to always or everysec, and a background
+# saving process (a background save or AOF log background rewriting) is
+# performing a lot of I/O against the disk, in some Linux configurations
+# Redis may block too long on the fsync() call. Note that there is no fix for
+# this currently, as even performing fsync in a different thread will block
+# our synchronous write(2) call.
+#
+# In order to mitigate this problem it's possible to use the following option
+# that will prevent fsync() from being called in the main process while a
+# BGSAVE or BGREWRITEAOF is in progress.
+#
+# This means that while another child is saving the durability of Redis is
+# the same as "appendfsync none", that in practical terms means that it is
+# possible to lost up to 30 seconds of log in the worst scenario (with the
+# default Linux settings).
+#
+# If you have latency problems turn this to "yes". Otherwise leave it as
+# "no" that is the safest pick from the point of view of durability.
+no-appendfsync-on-rewrite no
+
+# Automatic rewrite of the append only file.
+# Redis is able to automatically rewrite the log file implicitly calling
+# BGREWRITEAOF when the AOF log size will growth by the specified percentage.
+#
+# This is how it works: Redis remembers the size of the AOF file after the
+# latest rewrite (or if no rewrite happened since the restart, the size of
+# the AOF at startup is used).
+#
+# This base size is compared to the current size. If the current size is
+# bigger than the specified percentage, the rewrite is triggered. Also
+# you need to specify a minimal size for the AOF file to be rewritten, this
+# is useful to avoid rewriting the AOF file even if the percentage increase
+# is reached but it is still pretty small.
+#
+# Specify a percentage of zero in order to disable the automatic AOF
+# rewrite feature.
+
+auto-aof-rewrite-percentage 100
+auto-aof-rewrite-min-size 64mb
+
+################################ LUA SCRIPTING  ###############################
+
+# Max execution time of a Lua script in milliseconds.
+#
+# If the maximum execution time is reached Redis will log that a script is
+# still in execution after the maximum allowed time and will start to
+# reply to queries with an error.
+#
+# When a long running script exceed the maximum execution time only the
+# SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
+# used to stop a script that did not yet called write commands. The second
+# is the only way to shut down the server in the case a write commands was
+# already issue by the script but the user don't want to wait for the natural
+# termination of the script.
+#
+# Set it to 0 or a negative value for unlimited execution without warnings.
+lua-time-limit 5000
+
+################################## SLOW LOG ###################################
+
+# The Redis Slow Log is a system to log queries that exceeded a specified
+# execution time. The execution time does not include the I/O operations
+# like talking with the client, sending the reply and so forth,
+# but just the time needed to actually execute the command (this is the only
+# stage of command execution where the thread is blocked and can not serve
+# other requests in the meantime).
+#
+# You can configure the slow log with two parameters: one tells Redis
+# what is the execution time, in microseconds, to exceed in order for the
+# command to get logged, and the other parameter is the length of the
+# slow log. When a new command is logged the oldest one is removed from the
+# queue of logged commands.
+
+# The following time is expressed in microseconds, so 1000000 is equivalent
+# to one second. Note that a negative number disables the slow log, while
+# a value of zero forces the logging of every command.
+slowlog-log-slower-than 10000
+
+# There is no limit to this length. Just be aware that it will consume memory.
+# You can reclaim memory used by the slow log with SLOWLOG RESET.
+slowlog-max-len 128
+
+############################### ADVANCED CONFIG ###############################
+
+# Hashes are encoded using a memory efficient data structure when they have a
+# small number of entries, and the biggest entry does not exceed a given
+# threshold. These thresholds can be configured using the following directives.
+hash-max-ziplist-entries 512
+hash-max-ziplist-value 64
+
+# Similarly to hashes, small lists are also encoded in a special way in order
+# to save a lot of space. The special representation is only used when
+# you are under the following limits:
+list-max-ziplist-entries 512
+list-max-ziplist-value 64
+
+# Sets have a special encoding in just one case: when a set is composed
+# of just strings that happens to be integers in radix 10 in the range
+# of 64 bit signed integers.
+# The following configuration setting sets the limit in the size of the
+# set in order to use this special memory saving encoding.
+set-max-intset-entries 512
+
+# Similarly to hashes and lists, sorted sets are also specially encoded in
+# order to save a lot of space. This encoding is only used when the length and
+# elements of a sorted set are below the following limits:
+zset-max-ziplist-entries 128
+zset-max-ziplist-value 64
+
+# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
+# order to help rehashing the main Redis hash table (the one mapping top-level
+# keys to values). The hash table implementation Redis uses (see dict.c)
+# performs a lazy rehashing: the more operation you run into an hash table
+# that is rehashing, the more rehashing "steps" are performed, so if the
+# server is idle the rehashing is never complete and some more memory is used
+# by the hash table.
+#
+# The default is to use this millisecond 10 times every second in order to
+# active rehashing the main dictionaries, freeing memory when possible.
+#
+# If unsure:
+# use "activerehashing no" if you have hard latency requirements and it is
+# not a good thing in your environment that Redis can reply form time to time
+# to queries with 2 milliseconds delay.
+#
+# use "activerehashing yes" if you don't have such hard requirements but
+# want to free memory asap when possible.
+activerehashing yes
+
+# The client output buffer limits can be used to force disconnection of clients
+# that are not reading data from the server fast enough for some reason (a
+# common reason is that a Pub/Sub client can't consume messages as fast as the
+# publisher can produce them).
+#
+# The limit can be set differently for the three different classes of clients:
+#
+# normal -> normal clients
+# slave  -> slave clients and MONITOR clients
+# pubsub -> clients subcribed to at least one pubsub channel or pattern
+#
+# The syntax of every client-output-buffer-limit directive is the following:
+#
+# client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
+#
+# A client is immediately disconnected once the hard limit is reached, or if
+# the soft limit is reached and remains reached for the specified number of
+# seconds (continuously).
+# So for instance if the hard limit is 32 megabytes and the soft limit is
+# 16 megabytes / 10 seconds, the client will get disconnected immediately
+# if the size of the output buffers reach 32 megabytes, but will also get
+# disconnected if the client reaches 16 megabytes and continuously overcomes
+# the limit for 10 seconds.
+#
+# By default normal clients are not limited because they don't receive data
+# without asking (in a push way), but just after a request, so only
+# asynchronous clients may create a scenario where data is requested faster
+# than it can read.
+#
+# Instead there is a default limit for pubsub and slave clients, since
+# subscribers and slaves receive data in a push fashion.
+#
+# Both the hard or the soft limit can be disabled just setting it to zero.
+client-output-buffer-limit normal 0 0 0
+client-output-buffer-limit slave 256mb 64mb 60
+client-output-buffer-limit pubsub 32mb 8mb 60
+
+################################## INCLUDES ###################################
+
+# Include one or more other config files here.  This is useful if you
+# have a standard template that goes to all Redis server but also need
+# to customize a few per-server settings.  Include files can include
+# other files, so use this wisely.
+#
+# include /path/to/local.conf
+# include /path/to/other.conf

data/templates/resque_initd

@@ -0,0 +1,24 @@
+#! /bin/sh
+
+cd_path="#{current_path}"
+export_gem_home="export GEM_HOME=#{rvm_path}/gems/#{rvm_ruby_string}"
+
+case "$1" in
+  start)
+        echo -n "Starting #{file}: "
+                su - deploy -c "cd $cd_path && $export_gem_home && bundle exec rake RAILS_ENV=#{rails_env} QUEUE=#{queue} VERBOSE=1 PIDFILE=tmp/pids/#{file}.pid resque:work >> log/#{file}.log 2>&1 &"
+        echo "OK."
+        ;;
+  stop)
+        echo -n "Stopping #{file}: "
+                su - deploy -c "kill -QUIT `cat $cd_path/tmp/pids/#{file}.pid` && rm -f $cd_path/tmp/pids/#{file}.pid && exit 0"
+        echo "done."
+        ;;
+      *)
+            N=/etc/init.d/#{file}
+            echo "Usage: $N {start|stop}" >&2
+            exit 1
+            ;;
+esac
+
+exit 0

data/templates/resque_monitd

@@ -0,0 +1,7 @@
+check process #{file}
+  with pidfile #{current_path}/tmp/pids/#{file}.pid
+  start program = "/etc/init.d/#{file} start" with timeout 60 seconds
+  stop program = "/etc/init.d/#{file} stop"
+  #{depends}
+  if totalmem is greater than #{mem} MB for 10 cycles then restart  # eating up memory?
+  group #{resque_prefix}_resque_workers

data/templates/usr/local/bin/redis-check-queue

@@ -0,0 +1,2 @@
+#!/bin/bash
+/usr/local/bin/redis-cli -h %RESQUE_HOST% -p %RESQUE_PORT% ping

metadata

@@ -0,0 +1,111 @@
+--- !ruby/object:Gem::Specification
+name: capistrano-resque_monit
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+platform: ruby
+authors:
+- Gino Clement
+- Jeremy Wadsack
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2015-07-15 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: capistrano
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.6'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.6'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+description: A set of Capistrano scripts for configuring resque workers to be monitored
+  by monit
+email:
+- ginoclement@gmail.com
+- jeremy@keylimetoolbox.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- capistrano-resque_monit.gemspec
+- lib/capistrano/resque_monit.rb
+- lib/capistrano/resque_monit/monit.rb
+- lib/capistrano/resque_monit/resque.rb
+- lib/capistrano/resque_monit/tasks.rb
+- lib/capistrano/resque_monit/version.rb
+- templates/etc/init.d/monit
+- templates/etc/init.d/resque_scheduler
+- templates/etc/monit.d/alert
+- templates/etc/monit.d/logging
+- templates/etc/monit.d/nginx
+- templates/etc/monit.d/redis
+- templates/monitrc
+- templates/redis.conf
+- templates/resque_initd
+- templates/resque_monitd
+- templates/usr/local/bin/redis-check-queue
+homepage: https://github.com/keylimetoolbox/capinstrano-resque_monit
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.4.6
+signing_key: 
+specification_version: 4
+summary: Deploying Resque and Monit using Capistrano.
+test_files: []