Puma - 使用配置文件运行服务器时显示完整日志

Question

我安装了

puma

gem，当我通过

rails s

启动 Rails 服务器时，我可以看到完整的输出：

$ rails s 
/Users/serj/.rvm/gems/ruby-2.2.1@email_platform/gems/htmlentities-4.3.2/lib/htmlentities/mappings/expanded.rb:465: warning: duplicated key at line 466 ignored: "inodot"
=> Booting Puma
=> Rails 4.1.12 application starting in development on http://0.0.0.0:3000
=> Run `rails server -h` for more startup options
=> Notice: server is listening on all interfaces (0.0.0.0). Consider using 127.0.0.1 (--binding option)
=> Ctrl-C to shutdown server
Puma 2.12.3 starting...
* Min threads: 0, max threads: 16
* Environment: development
* Listening on tcp://0.0.0.0:3000


Started GET "/templates/41" for 127.0.0.1 at 2015-08-06 14:10:32 -0400
Cache read: accont_by_domain/demo.lvh.me ({:expires_in=>86400 seconds})
Dalli::Server#connect 127.0.0.1:11211
Cache fetch_hit: accont_by_domain/demo.lvh.me ({:expires_in=>86400 seconds})
Processing by TemplatesController#show as HTML
  Parameters: {"id"=>"41"}
  User Load (1.1ms)  SELECT  "users".* FROM "users"  WHERE "users"."id" = $1 LIMIT 1  [["id", 543]]

但是，当我尝试通过提供配置文件来运行 puma 时，我再也看不到完整日志了：

$ bundle exec puma -C config/puma.rb
[56872] Puma starting in cluster mode...
[56872] * Version 2.12.3 (ruby 2.2.1-p85), codename: Plutonian Photo Shoot
[56872] * Min threads: 1, max threads: 1
[56872] * Environment: development
[56872] * Process workers: 2
[56872] * Preloading application
/Users/serj/.rvm/gems/ruby-2.2.1@email_platform/gems/htmlentities-4.3.2/lib/htmlentities/mappings/expanded.rb:465: warning: duplicated key at line 466 ignored: "inodot"
[56872] * Listening on tcp://0.0.0.0:3000
[56872] ! WARNING: Detected 1 Thread(s) started in app boot:
[56872] ! #<Rack::MiniProfiler::FileStore::CacheCleanupThread:0x007fb58ccaa730@/Users/serj/.rvm/gems/ruby-2.2.1@email_platform/gems/rack-mini-profiler-0.9.7/lib/mini_profiler/storage/file_store.rb:47 sleep> - /Users/serj/.rvm/gems/ruby-2.2.1@email_platform/gems/rack-mini-profiler-0.9.7/lib/mini_profiler/storage/file_store.rb:65:in `sleep'
[56872] Use Ctrl-C to stop
[56872] - Worker 0 (pid: 56894) booted, phase: 0
[56872] - Worker 1 (pid: 56895) booted, phase: 0
[56894] 127.0.0.1 - - [06/Aug/2015:14:12:13 -0400] "GET /templates/41 HTTP/1.1" 200 45108 3.3802
[56894] 127.0.0.1 - - [06/Aug/2015:14:12:13 -0400] "GET /bootstrap-image-gallery.css?body=1 HTTP/1.1" 304 - 0.0379
[56894] 127.0.0.1 - - [06/Aug/2015:14:12:13 -0400] "GET /jquery.ui.autocomplete.css?body=1 HTTP/1.1" 304 - 0.0427
...

有没有办法像

rails s

那样显示日志？我希望具有与

rails s

相同的行为，而无需运行其他命令。可以吗？

我的美洲狮配置：

workers Integer(ENV['WEB_CONCURRENCY'] || 2)
threads_count = Integer(ENV['MAX_THREADS'] || 1)
threads threads_count, threads_count

preload_app!

rackup      DefaultRackup
port        ENV['PORT']     || 3000
environment ENV['RACK_ENV'] || 'development'

on_worker_boot do
  # Worker specific setup for Rails 4.1+
  # See: https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server#on-worker-boot
  ActiveRecord::Base.establish_connection
end

Answer 1

日志位于

log/<rails env>.log

。所以你可以（在单独的选项卡/窗口中）运行：

tail -f log/development.log

您将看到所有输出。如果您希望将 Rails 的输出合并到 puma 日志中，您可以随时将 Rails 日志记录到

STDOUT

:

config.logger = Logger.new(STDOUT)

Answer 2

我在 Puma github 自述文件中找到了这个命令：

$rails s Puma

这也会产生所需的行为。

编辑： 事实上，如此处所述，安装 Puma 后，rails 的命令应该会自动拾取它，而无需 Puma 参数。

Answer 3

如果您感兴趣的是日志，那么您可以跟踪实际的日志文件。事情会是这样的

tail -f log/development.log

。

Answer 4

如果您使用 foreman 或

Procfile

，您可以将

tail -f log

添加到您的

Procfile

。我用的就是这个：

# Procfile.dev
web: bundle exec puma -p $PORT
webpack: bin/webpack-dev-server
log: tail -f log/development.log

然后我像这样启动 Rails：

$> PORT=3000 foreman start -f Procfile.dev

实际上我的

.zshrc

中有一个别名：

alias railss='PORT=3000 foreman start -f Procfile.dev'

所以我可以简单地启动 Rails：

$> railss

Answer 5

就我而言，我尝试过

config.logger = Logger.new(STDOUT)

但是我收到了一堆日志错误：NoMethodError: #Logger 的未定义方法“沉默”:...

我找到的解决方案是添加到 config/environments/development.rb

logger           = ActiveSupport::Logger.new(STDOUT)
logger.formatter = config.log_formatter
config.logger    = ActiveSupport::TaggedLogging.new(logger)

鸣谢：https://github.com/rails/sprockets-rails/issues/376#issuecomment-287560399

Answer 6

它可能是由于 Puma 配置文件中的以下行而发生的：

workers Integer(ENV['WEB_CONCURRENCY'] || 2)

尝试删除此行或将工人设置为 0。

这样 Puma 将以单一模式运行并开始打印所有日志。