Rant! 100GB Log file in Nextcloud.
-
I don't disagree that logrotate is a sensible answer here, but making that the responsibility of the user is silly.
-
I have lost now not hours, but days debugging their terrible AIO container. Live production code stored in persistent volumes. Scattered files around the main drive in seemingly arbitrary locations. Environment variables that are consistently ignored/overrided. It's probably my number one example of worst docker containers and what not to do when designing your container.
-
Yeah, their AIO setup is just bad, the more "traditional" and community supported docker compose files work well, I've been using them for years. They're not perfect, but work well. Nextcloud is not bad per se, but just avoid their AIO docker.
-
It's too late for me now coz I didnt do my research and ive already migrated over, but good god ever loving fuck was the AIO container the hardest of all my services to set up.
Firstly, it throws a fit if you don't set up the filesystem specifically for php and the postgres db as if it were bare metal. Idk how or why every other container I use can deal with UID 568 but Nextcloud demands www-data and netdata users.
When that's done, you realise it won't run background tasks because it expects cron to be set up. You have to set a cronjob that enters the container to run the cron, all to avoid the "recommended" approach of using a second nextcloud instance just to run background tasks.
And finally, and maybe this is just a fault of TrueNAS' setup wizard but, I still had to enter the container shell to set up a bunch of basic settings like phone region. come on.
Straight up worse than installing it bare metal
-
Just use the official Docker AIO and it is very, very little trouble. It's by far the easiest way to use Nextcloud and the related services like Collabora and Talk.
-
I’ve only ever used the AIO and it’s the only one of my problem containers out of about 30. Would you mind pointing me to some decent community compose files? Thanks!!
-
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.
-
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.
-
Those should also all be secure by default. What is this, Windows?
-
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.
-
I stopped using Nextcloud a couple of years ago after it corrupted my encrypted storage. But I'm giving it a try again because of political emergency. But we sure need a long term replacement. Written in Rust or some other sane language.
-
The fact (IMHO) is that the logs shouldn't be there, in a persistent volume.
-
The price rboem is that the log file is inside the container in the www folder
-
Be too, and I went back to the standalone community container
-
for some helpful config, the below is the logging config I have and logs have never been an issue.
You can even add
'logfile' => '/some/location/nextcloud.log',to get the logs in a different place'logtimezone' => 'UTC', 'logdateformat' => 'Y-m-d H:i:s', 'loglevel' => 2, 'log_rotate_size' => 52428800, -
Wow, thanks for the heads up! I use Nextcloud AIO and backups take VERY long. I need to check about those logs!
Don't know if I'm just lucky or what, but it's been working really well for me and takes good care of itself for the most part. I'm a little shocked seeing so many complaints in this thread because elsewhere on the Internet that's the go-to method.
-
Good point!
-
Good suggestion, although I do feel it always comes back to this “many ways to do kind of the same thing” that surrounds the Linux ecosystem. Docker, podman, … some claim it’s better, I hear others say it’s not 100% compatible all the time. My point being more fragmentation.
-
Logration is the abc of the developer.
Why should I need 3rd party tools to fix the work of the developer?? -
At worst it saves in the config folder/volume where persistent stuff should be.
