Ensure logs are stored for 30 days #927
Description
Description
We store a copy of production.log and sidekiq.log files from the last 4 releases, which should normally ensure that we have 30 days worth of records.
But it seems that logs can be truncated during the week if they get too large, so we have gaps in logs. Sometimes after only a couple of days (while we still have logs from a point in time 4 weeks ago).
Possible Fix
Maybe we can increase the truncate limit to reduce the likelihood of gaps.
But it would be much better to move the log to the shared folder (like we already do for puma logs) so that we don't have gaps. We can set a reasonably high limit to allow for hopefully 30 days
The puma logs in the shared folder are rotated and compressed, so presumably this will happen for production.log too.