How do you manage your containers?

Would a self signed certificate be an option? Not sure if the hassel is worth with the applications on the phone.

If you like compose files: https://www.composerize.com/

docker run -it --rm -v <your-data-path>:/data -e SYNAPSE_SERVER_NAME=<your-public-address-subdomain> -e SYNAPSE_REPORT_STATS=no matrixdotorg/synapse:v1.136.0 generate:

name: <your project name>
services:
    synapse:
        stdin_open: true
        tty: true
        volumes:
            - <your-data-path>:/data
        environment:
            - SYNAPSE_SERVER_NAME=<your-public-address-subdomain>
            - SYNAPSE_REPORT_STATS=no
        image: matrixdotorg/synapse:v1.136.0
        command: generate

docker run -d --restart=always --name synapse -e SYNAPSE_REPORT_STATS=no -v <your-data-path>:/data -p 8008:8008 matrixdotorg/synapse:v1.136.0:

name: <your project name>
services:
    synapse:
        restart: always
        container_name: synapse
        environment:
            - SYNAPSE_REPORT_STATS=no
        volumes:
            - <your-data-path>:/data
        ports:
            - 8008:8008
        image: matrixdotorg/synapse:v1.136.0

Caddy makes HTTPS a breeze. I’ve tried nginx before but I never understood when and why I would need which setting.

What’s bad about hairpin NAT? Not having to maintain a local DNS server is nice.

Do you need one app for syncing caldav and another app for using the calendar?

https://www.loopia.com/ - ~10 euro/year for only DNS and ~100 euro/year for DNS, e-mail and web hosting.

A snapshot is like copying a the files in the snapshot to another location, while the original files remain as is and can be written to or read from.

As an example, if you have a folder, let’s say /important/secret/stuff, and you want to take a backup of it. You have to make sure that nothing is writing to those files while the backup is running, otherwise the backup risk being corrupted. (This is because if the backup starts to read the file, and halfway through the first part of the file changes, you now have a backuped file that half the old and half the new file).

With a snapshop, you can “copy” /important/secret/stuff to some other location, run a backup reading from this other location and then remove it. Any changes to the original files will not affect the backup since the backup is reading from the “copied” files (snapshot).

So what you do is take a snapshot before running the backup, have the backup read from the snapshot and when it is complete, remove the snapshot.