docs VS seaweedfs

I will recommend you review the documentation for the official Postgresql docker images which you can read here.

This is the full documentation for these images. Please note, this page has links to Docker official documents on volumes, etc., which are necessary to run images such as this.

We've just followed the official documentation to add a PostgreSQL database server. This will act as an application container, as our app will soon be depended on it. And in order to make sure that the database container is always started whenever we start our application container, we've added a new depends_on key to the app service and let it know which other service(s) it, well, depends on. This will make sure that the database server is up and running before the app. You may also have noticed that we've mounted volume to our database server's datapath a bit differently. This is known as "named volume". We'll discuss it a bit more in another part, it's not relevant to what we're learning here.

Nextcloud isn't hard to setup, follow the official doc https://github.com/docker-library/docs/blob/master/nextcloud/README.md

Looking at the setup for this (link here: https://github.com/docker-library/docs/blob/master/nextcloud/README.md), I am starting to understand a lot of the recent posts that we've seen & how much of a mess it still is :(

Coming back to nextcloud, the official readme of the nextcloud image has a few notes on how to set up both nextcloud versions.

Use the native command envstubst to replace the Auth Tokens in your Config File before starting NGINX. Example: https://github.com/docker-library/docs/tree/master/nginx#using-environment-variables-in-nginx-configuration-new-in-119

It's not clear why you want to split the web server (nginx) and the app (nextcloud). However, if you do have a good reason, you're in luck, they have a compose file that does just that: https://github.com/docker-library/docs/blob/master/nextcloud/README.md#base-version---fpm (version 2, but it'll work)

Whoops: WebDAV:

https://news.ycombinator.com/item?id=39417503

SeaweedFS supports WebDAV. https://github.com/seaweedfs/seaweedfs/wiki/WebDAV

I'm not able to find if both/restic supports mounting backups as WebDAV, but in theory there's nothing stopping you.

It's 100% user space (expose a rest service) and supported by a bunch of file-browsers with a bit of a network aware component to it as well.

If you want/need to take out the metadata, there's some nice solutions for that https://github.com/seaweedfs/seaweedfs

I posted this on https://github.com/seaweedfs/seaweedfs/discussions/5290

I like the idea of using SeaweedFS as an intermediate layer with object write notifications going to SQS, RabbitMQ, or a local file, which could also allow me to observe the changes to different files through a metric collection layer like Prometheus and Grafana.

> Theoretically they could swap with minio but last time we used it it was not a drop-in replacement yet.

Depends on whether AGPL v3 works for you or not (or whether you decide to pay them), I guess: https://min.io/pricing

I've actually been looking for more open alternatives, but haven't found much.

Zenko CloudServer seemed to be somewhat promising, but doesn't seem to be managed very actively: https://github.com/scality/cloudserver/issues/4986 (their Docker images on DockerHub were last updated 10 months ago, which is what the homepage links to; blog doesn't seem active since 2019, forums don't have much going on, despite some action on GitHub still)

There was also Garage, but that one is also AGPL v3: https://garagehq.deuxfleurs.fr/

The closest I got was discovering that SeaweedFS has an S3 compatible mode: https://github.com/seaweedfs/seaweedfs

SeaweedFS S3 Gateway for Joplin notes