improve log handling when using Docker

[rriemann]

Hello!

I am quite advanced with a docker-compose setup that integrates mastodon and the crossposter.

During debugging, I noticed that logs are put into logs/production.log. However, it would be much better if when launched from within docker, the logs would be send to STDERR or STDOUT. This way, they can be easily viewed with docker compose logs crossposter. Also, we can get logrotate for free.

I suggest that we add one line to the Dockerfile to make the webserver send output instead of to production.log to STDOUT and if it's an error, STDERR.

I quickly searched and found two possible paths:

add this to config/environment/test.rb (here: production.rb)

# Enable stdout logger
config.logger = Logger.new(STDOUT)

There seems to be also an environment variable: RAILS_LOG_TO_STDOUT=1.

In any case, if a log file remains in the docker container, it should respect a file size limit.

Best,
Robert

[renatolond]

Hey, yeah, on my production env I have RAILS_LOG_TO_STDOUT=enabled in my .env
I believe it's better to set that one directly in the Dockerfile directly, since I doubt anyone would rather have it on a file in a Docker setup 🤔
Would you like to do it or would you rather I pick it up here?

[rriemann]

I'm in deep troubles with getting the mastodon streaming component working. I would appreciate it you can make this one happen.

[renatolond]

Sorry, didn't had time before, should be fixed now :)