Why is that? Really? The Dev should replace a system function? And implement over and over again the same errors when logrotate exist?
Probably, but still, if they are, just rotate them.
Just basic checks I prefer to ensure, not leave to distribution good faith. If all is set, good to go. Otherwise, fix and move on.
Specially with self hosted stuff that is a bit more custom than the usual.
Agreed, but going container route those nice basic practices are dead.
And also, being mextcloud a php service, of can’t by definition ship with a logrotate config too, because its never packaged by your repo.
Are you crazy? I understand that we are used to dumbed down stuff, but come on…
Rotating logs is in the ABC of any sysadmin, even before backups.
First, secure your ssh logins, then secure your logs, then your fail2ban then your backups…
To me, that’s in the basic stuff you must always ensure.
You should always setup logrotate. Yes the good old Linux logrotate…
Dockers images are often incoherent and just different from one a other so much that you should never give something as expected and doublecheck the basics.
Docker was never meant do deploy services, and I shows.