puma 3.12.1 → 5.3.2

data/tools/jungle/init.d/run-puma

@@ -1,18 +0,0 @@
-#!/bin/bash
-
-# on system boot, and root have no rbenv installed,
-#   after start-stop-daemon switched to current user, we have to init rbenv
-if [ -d "$HOME/.rbenv/bin" ]; then
-  PATH="$HOME/.rbenv/bin:$HOME/.rbenv/shims:$PATH"
-  eval "$(rbenv init -)"
-elif [ -d "/usr/local/rbenv/bin" ]; then
-  PATH="/usr/local/rbenv/bin:/usr/local/rbenv/shims:$PATH"
-  eval "$(rbenv init -)"
-elif [ -f /usr/local/rvm/scripts/rvm ]; then
-  source /etc/profile.d/rvm.sh
-elif [ -f "$HOME/.rvm/scripts/rvm" ]; then
-  source "$HOME/.rvm/scripts/rvm"
-fi
-
-app=$1; config=$2; log=$3;
-cd $app && exec bundle exec puma -C $config >> $log 2>&1

data/tools/jungle/upstart/README.md

@@ -1,61 +0,0 @@
-# Puma as a service using Upstart
-
-Manage multiple Puma servers as services on the same box using Ubuntu upstart.
-
-## Installation 
-
-    # Copy the scripts to services directory 
-    sudo cp puma.conf puma-manager.conf /etc/init
-    
-    # Create an empty configuration file
-    sudo touch /etc/puma.conf
-
-## Managing the jungle 
-
-Puma apps are referenced in /etc/puma.conf by default. Add each app's path as a new line, e.g.:
-
-```
-/home/apps/my-cool-ruby-app
-/home/apps/another-app/current
-```
-
-Start the jungle running:
-
-`sudo start puma-manager`
-
-This script will run at boot time.
-
-Start a single puma like this:
-
-`sudo start puma app=/path/to/app`
-
-## Logs
-
-Everything is logged by upstart, defaulting to `/var/log/upstart`.
-
-Each puma instance is named after its directory, so for an app called `/home/apps/my-app` the log file would be `/var/log/upstart/puma-_home_apps_my-app.log`.
-
-## Conventions 
-
-* The script expects:
-  * a config file to exist under `config/puma.rb` in your app. E.g.: `/home/apps/my-app/config/puma.rb`.
-  * a temporary folder to put the PID, socket and state files to exist called `tmp/puma`. E.g.: `/home/apps/my-app/tmp/puma`. Puma will take care of the files for you.
-
-You can always change those defaults by editing the scripts.
-
-## Here's what a minimal app's config file should have
-
-```
-pidfile "/path/to/app/tmp/puma/pid"
-state_path "/path/to/app/tmp/puma/state"
-activate_control_app
-```
-
-## Before starting...
-
-You need to customise `puma.conf` to:
-
-* Set the right user your app should be running on unless you want root to execute it!
-  * Look for `setuid apps` and `setgid apps`, uncomment those lines and replace `apps` to whatever your deployment user is.
-  * Replace `apps` on the paths (or set the right paths to your user's home) everywhere else.
-* Uncomment the source lines for `rbenv` or `rvm` support unless you use a system wide installation of Ruby.

data/tools/jungle/upstart/puma-manager.conf

@@ -1,31 +0,0 @@
-# /etc/init/puma-manager.conf - manage a set of Pumas
-
-# This example config should work with Ubuntu 12.04+.  It
-# allows you to manage multiple Puma instances with
-# Upstart, Ubuntu's native service management tool.
-#
-# See puma.conf for how to manage a single Puma instance.
-#
-# Use "stop puma-manager" to stop all Puma instances.
-# Use "start puma-manager" to start all instances.
-# Use "restart puma-manager" to restart all instances.
-# Crazy, right?
-#
-
-description "Manages the set of puma processes"
-
-# This starts upon bootup and stops on shutdown
-start on runlevel [2345]
-stop on runlevel [06]
-
-# Set this to the number of Puma processes you want
-# to run on this machine
-env PUMA_CONF="/etc/puma.conf"
-
-pre-start script
-  for i in `cat $PUMA_CONF`; do
-    app=`echo $i | cut -d , -f 1`
-    logger -t "puma-manager" "Starting $app"
-    start puma app=$app
-  done
-end script

data/tools/jungle/upstart/puma.conf

@@ -1,69 +0,0 @@
-# /etc/init/puma.conf - Puma config
-
-# This example config should work with Ubuntu 12.04+.  It
-# allows you to manage multiple Puma instances with
-# Upstart, Ubuntu's native service management tool.
-#
-# See puma-manager.conf for how to manage all Puma instances at once.
-#
-# Save this config as /etc/init/puma.conf then manage puma with:
-#   sudo start puma app=PATH_TO_APP
-#   sudo stop puma app=PATH_TO_APP
-#   sudo status puma app=PATH_TO_APP
-#
-# or use the service command:
-#   sudo service puma {start,stop,restart,status}
-#
-
-description "Puma Background Worker"
-
-# no "start on", we don't want to automatically start
-stop on (stopping puma-manager or runlevel [06])
-
-# change apps to match your deployment user if you want to use this as a less privileged user (recommended!)
-setuid apps
-setgid apps
-
-respawn
-respawn limit 3 30
-
-instance ${app}
-
-script
-# this script runs in /bin/sh by default
-# respawn as bash so we can source in rbenv/rvm
-# quoted heredoc to tell /bin/sh not to interpret
-# variables
-
-# source ENV variables manually as Upstart doesn't, eg:
-#. /etc/environment
-
-exec /bin/bash <<'EOT'
-  # set HOME to the setuid user's home, there doesn't seem to be a better, portable way
-  export HOME="$(eval echo ~$(id -un))"
-
-  if [ -d "/usr/local/rbenv/bin" ]; then
-    export PATH="/usr/local/rbenv/bin:/usr/local/rbenv/shims:$PATH"
-  elif [ -d "$HOME/.rbenv/bin" ]; then
-    export PATH="$HOME/.rbenv/bin:$HOME/.rbenv/shims:$PATH"
-  elif [ -f  /etc/profile.d/rvm.sh ]; then
-    source /etc/profile.d/rvm.sh
-  elif [ -f /usr/local/rvm/scripts/rvm ]; then
-    source /etc/profile.d/rvm.sh
-  elif [ -f "$HOME/.rvm/scripts/rvm" ]; then
-    source "$HOME/.rvm/scripts/rvm"
-  elif [ -f /usr/local/share/chruby/chruby.sh ]; then
-    source /usr/local/share/chruby/chruby.sh
-    if [ -f /usr/local/share/chruby/auto.sh ]; then
-      source /usr/local/share/chruby/auto.sh
-    fi
-    # if you aren't using auto, set your version here
-    # chruby 2.0.0
-  fi
-
-  cd $app
-  logger -t puma "Starting server: $app"
-
-  exec bundle exec puma -C config/puma.rb
-EOT
-end script