Files
dokku/plugins
Jose Diaz-Gonzalez 64cc239d5b fix: use copytruncate in logrotate commands
While using create is more correct, logs in Dokku are considered ephemeral, and thus shouldn't be considered subject to the more comprehensive log retention standards one might require out of a logging system.

By switching to copytruncate, we can ensure that logs mounted from within containers do not have that matched the old settings (closes #6633) and cases where the log file is written by a user other than the one specified in the old logrotate settings (closes #4000).
2024-03-12 23:49:49 -04:00
..
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 19:54:52 -05:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00
2024-03-06 16:40:18 +00:00