--dev ignores any per-process log file about procodile HOT 4 CLOSED

FYI contents of my Profile.options

app_name: roomballot
log_root: log
pid_root: tmp/pids
console_command: bundle exec rails console
env:
  RAILS_ENV: production
  RAILS_MAX_THREADS: 16
processes:
  web:
    log_file_name: puma.log
    restart_mode: usr2
    term_signal: INT
  worker:
    log_file_name: sidekiq.log
    restart_mode: start-term
    term_signal: INT
  cron:
    log_file_name: clockwork.log
    restart_mode: start-term
    term_signal: INT

from procodile.

I don't believe Procodile ever uses a file called production.log. With --dev enabled, it should be running in the foreground with all output going to STDOUT. Rails will use production.log itself though and with RAILS_ENV set to production it will go there. If you change RAILS_ENV to development the Rails log will go to development.log.

from procodile.

I should also have said that the log managed by procodile is just the output of STDOUT. Rails itself doesn't log to STDOUT by default so that'll always go to files. You could change this behaviour though with something like the below in your config/application.rb file.

config.logger = Logger.new(STDOUT)

from procodile.

Ah I see now - just starting out with Rails so thank you!

After a bit of research I actually ended up going for Logger.new('log/rails.log') instead which seems to do the trick.

from procodile.