我如何使用puma的配置文件？
我按照本指南记录了存储在app的config目录中的puma.rb文件。
该指南有点夸张，但这是我认为puma.rb文件的作用。 而不是像这样运行疯狂的命令来让puma在指定的套接字上运行：
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
然后你可以进入应用程序的root并运行一个简单的命令
“彪马”
并且将遵循在puma.rb设置的参数。 不幸的是，这似乎对我不起作用。
至少，我在一个小测试应用程序的根目录中运行puma ，并且没有.sock文件出现在/home/starkers/Documents/alpha/tmp/sockets那么这是否意味着它不起作用？
我该如何工作？ 我在本地开发机器上，所以可能会以某种方式导致此错误？ 运行时是否需要传入参数
puma ？
我也被困在试图找到puma配置文件的文档，但我确实发现一体化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
如果定义了一个环境 – 在您的示例中就是这种情况 – 配置文件是从config/puma/[environment].rb而不是config/puma.rb 。
只需将config/puma.rb移动到config/puma/production.rb 。
阅读Puma文档以获取更多详细信息： 配置文件
这将有效：
puma -C config/puma.rb
你需要告诉puma在哪里找到你的rackup文件你可以把它放在你的配置中：
rackup DefaultRackup
它看起来像是一个修复程序合并到master： https ： //github.com/puma/puma/pull/271