Elvith Ma'for

Most importantly: Never ask them how they did solve their problems!

Yeah, but tomatoes are berries and thus fruit, not vegetables

https://http.cat/404

It is Setting Orange 26 Bureaucracy 3191 YOLD (Year Of the Linux Desktop)

Somehow I feel like mentioning Nix and NixOS is the new ‘I use arch btw’.

(No offense, but reading the ‘I use arch btw’ and then your response right after made me realize this)

Wat

For me it was usually that the config that I need to serve a site with TLS is quite short, there are sensible defaults and many things (e.g. websockets) just work without further declaration. That’s especially important if you want to host a container that has some lacking documentation about usage of reverse proxies, as most things “just work fine” for me.

And using a simple include directive, you can even replicate ‘sites-available’ and ‘sites-enabled’ behaviour. My standard Caddyfile just sets up the log file format and location and basic Let Encrypt values. Then it includes /foo/bar/sites-available/*. Every deployment/container now has its own Caddyfile that just gets linked there.

To be fair, when I open that link, I get light gray text on a dark brown-or-yellow-greyish background which isn’t that easily readable for me - at least contrast wise.

Rule 34 for FLOSS ¯\_(ツ)_/¯

Everything’s important and because that overwhelms you and you do not know what to prioritize, nothings important to you in the end

Do you happen to know of any self hosted report-ingestion, that allows me to check my csp and somewhat visualize them? I know there are services like report-uri and such, but they do cost a monthly fee and probably also have a privacy impact for my visitors

I get LFTP and somewhat cron, but why OpenSSH? You can also SSH to the host and get into the container from there.

ITry to keep containers minimal, meaning only add what you absolutely need. Also I advise you to keep/consider the content of the container as immutable. If something’s wrong, throw it away and restart with aa clean container. Data that you download should reside on a volume mapped to the container and this can usually also be accessed from the host. Same for any LFTP/cron config, etc.

So, what exactly is you plan why you need to SSH into the container itself? This post smells a bit like a XY Problem.

A quick google reveals that there are ready to go docker images with LFTP (which weighs about 7.5MB), which might be completely suitable for your need depending on your use case? https://hub.docker.com/r/minidocks/lftp/

Made in silicone valley

The door is obviously open. Not sure about the wheel, though…

assert IsEven(-2);

I only host Nextcloud in an old setup (read pure PHP, MariaDB, Apache - no docker, etc.)

That server is set-up to be snapshotted daily. Also there’s a script running about 30 min before each snap shot that will also dump the database to disk (as otherwise the snapshot might contain a random state of the database). It’s not perfect, but it works - also because everything of this is done in the night, when I do not use the system, so chances are really low, that the snapshot of the disk and the database dump in it are not desynchronized too much.

I do not know what’s the best practice for a modern Nextcloud setup with docker is or how to handle the other two…

Just a quick add on: not only do and automate backups - do also test them every now and then.

As you mentioned Immich, Nextcloud and Radicale - don’t forget to make regular backups. If you haven’t automated them, that’s your next project now ;)

I think he’s searching for sarcasm, no?

Guess why he came with a truck and not on a cargo bike…