我正在关注
this guide,它记录了存储在应用程序的config目录中的puma.rb文件.
该指南有点flakey,但这是我假设puma.rb文件.而不是运行这样的疯狂命令,以获得美洲豹在指定的套接字上运行：
bundle exec puma -e production -b unix:///var/run/my_app.sock
您可以在puma.rb文件中指定端口,pid,会话和其他参数,如下所示：
rails_env = ENV['RAILS_ENV'] || 'production' threads 4,4 bind "/home/starkers/Documents/alpha/tmp/socket" pidfile "/home/starkers/Documents/alpha/tmp/pid" state_path "/home/starkers/Documents/alpha/tmp/state" activate_control_app
然后你可以cd进入应用程序的根目录并运行一个简单的命令
“彪马”
并且将遵循在puma.rb中设置的参数.不幸的是,这似乎不适合我.
至少,我在一个小测试应用程序的根目录下运行了美洲狮,没有.sock文件出现
/ home / starkers / Documents / alpha / tmp / sockets是不是意味着它不工作？
我该如何让这个工作？我在一台本地开发机器上,那可能会导致这个错误呢？是否有一个参数,我需要在运行时传入
美洲狮
解决方法
我也试图找到关于美洲狮配置文件的文档,但我确实发现
the all-in-one config.ru文件有用.我已将格式化在此以备将来参考：
# The directory to operate out of.
# The default is the current directory.
directory '/u/apps/lolcat'
# Load “path” as a rackup file.
# The default is “config.ru”.
rackup '/u/apps/lolcat/config.ru'
# Set the environment in which the rack's app will run. The value must be a string.
# The default is “development”.
environment 'production'
# Daemonize the server into the background. Highly suggest that
# this be combined with “pidfile” and “stdout_redirect”.
# The default is “false”.
daemonize
daemonize false
# Store the pid of the server in the file at “path”.
pidfile '/u/apps/lolcat/tmp/pids/puma.pid'
# Use “path” as the file to store the server info state. This is
# used by “pumactl” to query and control the server.
state_path '/u/apps/lolcat/tmp/pids/puma.state'
# Redirect STDOUT and STDERR to files specified. The 3rd parameter
# (“append”) specifies whether the output is appended,the default is
# “false”.
stdout_redirect '/u/apps/lolcat/log/stdout','/u/apps/lolcat/log/stderr'
stdout_redirect '/u/apps/lolcat/log/stdout','/u/apps/lolcat/log/stderr',true
# Disable request logging.
# The default is “false”.
quiet
# 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'
# Listens on port 7001
# The default is 9292
port 7001
# 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
# 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 }
那些设置然后会进入一个ruby文件(例如config / puma.rb),然后Starkers说,你可以运行它
puma -C config/puma.rb