6ace422c29
Conflicts: Gemfile Gemfile.lock
93 lines
3 KiB
Text
93 lines
3 KiB
Text
#!/usr/bin/env puma
|
|
|
|
# Start Puma with next command:
|
|
# RAILS_ENV=production bundle exec puma -C ./config/puma.rb
|
|
|
|
# uncomment and customize to run in non-root path
|
|
# note that config/gitlab.yml web path should also be changed
|
|
# ENV['RAILS_RELATIVE_URL_ROOT'] = "/gitlab"
|
|
|
|
application_path = '/home/git/gitlab'
|
|
directory application_path
|
|
environment 'production'
|
|
daemonize true
|
|
pidfile "#{application_path}/tmp/pids/puma.pid"
|
|
state_path "#{application_path}/tmp/pids/puma.state"
|
|
stdout_redirect "#{application_path}/log/puma.stdout.log", "#{application_path}/log/puma.stderr.log"
|
|
|
|
# Configure “min” to be the minimum number of threads to use to answer
|
|
# requests and “max” the maximum.
|
|
#
|
|
# The default is “0, 16”.
|
|
#
|
|
# threads 0, 16
|
|
|
|
# Bind the server to “url”. “tcp://”, “unix://” and “ssl://” are the only
|
|
# accepted protocols.
|
|
#
|
|
# The default is “tcp://0.0.0.0:9292”.
|
|
#
|
|
# bind 'tcp://0.0.0.0:9292'
|
|
# bind 'unix:///var/run/puma.sock'
|
|
# bind 'unix:///var/run/puma.sock?umask=0777'
|
|
# bind 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert'
|
|
bind "unix://#{application_path}/tmp/sockets/gitlab.socket"
|
|
|
|
# Instead of “bind 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert'” you
|
|
# can also use the “ssl_bind” option.
|
|
#
|
|
# ssl_bind '127.0.0.1', '9292', { key: path_to_key, cert: path_to_cert }
|
|
|
|
# Code to run before doing a restart. This code should
|
|
# close log files, database connections, etc.
|
|
#
|
|
# This can be called multiple times to add code each time.
|
|
#
|
|
# on_restart do
|
|
# puts 'On restart...'
|
|
# end
|
|
|
|
# Command to use to restart puma. This should be just how to
|
|
# load puma itself (ie. 'ruby -Ilib bin/puma'), not the arguments
|
|
# to puma, as those are the same as the original process.
|
|
#
|
|
# restart_command '/u/app/lolcat/bin/restart_puma'
|
|
|
|
# === Cluster mode ===
|
|
|
|
# How many worker processes to run.
|
|
#
|
|
# The default is “0”.
|
|
#
|
|
# workers 2
|
|
|
|
# GitLab cluster mode recommendations
|
|
# If you have more than 1 GB RAM, uncomment one of the following lines:
|
|
#
|
|
# workers 2 # if you have at least 1.5 GB RAM
|
|
# workers 3 # if you have at least 2 GB RAM
|
|
# workers 4 # if you have at least 2.5 GB RAM
|
|
|
|
# Code to run when a worker boots to setup the process before booting
|
|
# the app.
|
|
#
|
|
# This can be called multiple times to add hooks.
|
|
#
|
|
# on_worker_boot do
|
|
# puts 'On worker boot...'
|
|
# end
|
|
|
|
# === Puma control rack application ===
|
|
|
|
# Start the puma control rack application on “url”. This application can
|
|
# be communicated with to control the main server. Additionally, you can
|
|
# provide an authentication token, so all requests to the control server
|
|
# will need to include that token as a query parameter. This allows for
|
|
# simple authentication.
|
|
#
|
|
# Check out https://github.com/puma/puma/blob/master/lib/puma/app/status.rb
|
|
# to see what the app has available.
|
|
#
|
|
# activate_control_app 'unix:///var/run/pumactl.sock'
|
|
# activate_control_app 'unix:///var/run/pumactl.sock', { auth_token: '12345' }
|
|
# activate_control_app 'unix:///var/run/pumactl.sock', { no_token: true }
|