this post was submitted on 23 Feb 2025
59 points (88.3% liked)

Selfhosted

59939 readers
519 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
59
Rant! 100GB Log file in Nextcloud. (lemmy.world)
submitted 1 year ago by MTK@lemmy.world to c/selfhosted@lemmy.world
75 comments fedilink hide all child comments
 

I set it to debug at somepoint and forgot maybe? Idk, but why the heck does the default config of the official Docker is to keep all logs, forever, in a single file woth no rotation?

Feels like 101 of log files. Anyway, this explains why my storage recipt grew slowly but unexpectedly.

you are viewing a single comment's thread
view the rest of the comments
[–] scrubbles@poptalk.scrubbles.tech 8 points 1 year ago (2 children)

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.

[–] ilmagico@lemmy.world 5 points 1 year ago (1 children)

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.

[–] grimer@lemmy.world 3 points 1 year ago (1 children)

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!!

[–] ilmagico@lemmy.world 4 points 1 year ago (1 children)

Well, here's the official "community maintained" docker repo:

https://github.com/nextcloud/docker

https://hub.docker.com/_/nextcloud

There's a section about docker compose, I have my own scripts but I believe I derived them from there at some point (my memory is a bit fuzzy). I use the fpm-alpine image, if it matters.

[–] grimer@lemmy.world 1 points 1 year ago

That works! Thank you!

[–] peregus@lemmy.world 3 points 1 year ago (1 children)

Be too, and I went back to the standalone community container