I'm working on a new structured logging gem (https://github.com/DocSpring/logstruct) and I've set up structured logging for dotenv-rails. I was just a bit confused about how it's supposed to work and if the current behavior is intentional or not.
In a default brand new Rails app, I only see dotenv messages in log/development.log, not in the terminal when running rails server.
From what I can tell, this happens because dotenv initializes very early in the boot process, before Rails has finished setting up its logger. Rails attaches the ActiveSupport::Logger.broadcast($stdout) during the :initialize_logger step, but dotenv logs its “Loaded .env.*” and “Set …” messages just before that. By the time Rails has wired STDOUT into Rails.logger, dotenv has already replayed its buffered logs into the file logger only.
In my own Rails app, I've changed logging so that everything goes to stdout immediately and I don't even have a development.log file, so I hadn't come across this issue before. I was just curious to know if the behavior is intentional and if I should try to preserve this when I set up the structured logging integration in LogStruct.
I'm working on a new structured logging gem (https://github.com/DocSpring/logstruct) and I've set up structured logging for dotenv-rails. I was just a bit confused about how it's supposed to work and if the current behavior is intentional or not.
In a default brand new Rails app, I only see dotenv messages in
log/development.log, not in the terminal when running rails server.From what I can tell, this happens because
dotenvinitializes very early in the boot process, before Rails has finished setting up its logger. Rails attaches theActiveSupport::Logger.broadcast($stdout)during the:initialize_loggerstep, butdotenvlogs its “Loaded .env.*” and “Set …” messages just before that. By the time Rails has wiredSTDOUTintoRails.logger,dotenvhas already replayed its buffered logs into the file logger only.In my own Rails app, I've changed logging so that everything goes to stdout immediately and I don't even have a
development.logfile, so I hadn't come across this issue before. I was just curious to know if the behavior is intentional and if I should try to preserve this when I set up the structured logging integration in LogStruct.