Probably, but still, if they are, just rotate them.
Shimitar
joined 1 month ago
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.
With my bike does it count? If so, yesterday multiple times to avoid speed bumps on the road.
Plot twist: op is your coworker
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.
You should always setup logrotate. Yes the good old Linux logrotate...
The VPS is required specially if you, like me, are behind CG-NAT with no way to escape from it. Using a VPS (or any other kind of server with a public IP). Using a VPS is the cheapest option...
residential IPs can be blocked for ports like 80, 443, 22 and the email ports in general (25, etc), using a non-residential IP could give a better experience. Moreover, even if not behind CG-NAT, having a public static and not-changing IP is a good advantage.
Everything is hosted locally! the VPS is only a tunnel between internet and the home server.
I have documented my journey here: https://wiki.gardiol.org/
On short, rent a vps and setup wireguard, then start self hosting everithing you can put yours hands on!!
Is this real or a joke?
Hey, you forget about Gentoo Linux!
The real distro for newbies... (Provided the newbies are expert cs graduated and crazy nerds...)
All depends on what a beginner is... Not all beginners are tech illiterates or people who only want to use office.
Why is that? Really? The Dev should replace a system function? And implement over and over again the same errors when logrotate exist?