Commit 2995ff12 authored by Andrew Newdigate's avatar Andrew Newdigate Committed by Kamil Trzciński

Include puma logs alongside rails logs in GDK

Currently puma logs are emitted to a different location than rails logs.
In development environments, having a single stream of logs for puma
and rails simplifies things and ensures that developers will see puma
errors, instead of having them emitted to a file that is not usually
checked.
parent c622832c
...@@ -14,9 +14,13 @@ rackup 'config.ru' ...@@ -14,9 +14,13 @@ rackup 'config.ru'
pidfile '/home/git/gitlab/tmp/pids/puma.pid' pidfile '/home/git/gitlab/tmp/pids/puma.pid'
state_path '/home/git/gitlab/tmp/pids/puma.state' state_path '/home/git/gitlab/tmp/pids/puma.state'
stdout_redirect '/home/git/gitlab/log/puma.stdout.log', ## Uncomment the lines if you would like to write puma stdout & stderr streams
'/home/git/gitlab/log/puma.stderr.log', ## to a different location than rails logs.
true ## When using GitLab Development Kit, by default, these logs will be consumed
## by runit and can be accessed using `gdk tail rails-web`
# stdout_redirect '/home/git/gitlab/log/puma.stdout.log',
# '/home/git/gitlab/log/puma.stderr.log',
# true
# Configure "min" to be the minimum number of threads to use to answer # Configure "min" to be the minimum number of threads to use to answer
# requests and "max" the maximum. # requests and "max" the maximum.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment