I ran nextcloud in docker-compose for 2 years, with nginx doing SSL termination in front. Granted I wasn't using the official image; I use the linuxserver.io releases for all my other services so I use them for this, too. Nextcloud's config is all in the DB, except for database and cache connection information in a single config file. PHP's config is in a separate file and some env vars (eg timezone).
I've recently moved it into my home k3s cluster (yeah, i'm one of those people), which means traefik is my new reverse proxy. Works fine. I found I can get traefik to do the DAV redirects at least with the k8s Ingress config, but I don't need to since the linuxserver image includes the redirects in its' nginx configuration.
I am with you. But. It's incredible how so many open source projects keep on delivering docker-compose files that either are not compatible with a reverse proxy or bundle a reverse proxy themselves.
It seems like the use case of having traefik/ngninx as a RP which does the SSL termination over how many services you want is fringe practice. Most of the apps/services I encountered could be blind to a RP but I often have to play around it.
> I want to have confidence that I can restore a db + files and have a working service come back up. At the moment, I don't trust Nextcloud to always come back up.
Well. Today OVH tried to upgrade things and it broke my VPS AND my owncloud db. Hopefully I had some sql dump backup but the DB was so borked I couldn't login in it even from root inside the container or in any other way.
I mean: don't trust the app provider to do the backup, set something up yourself.
> (I can't seem to make a bullet point list on HN)
For short points: indent with two spaces (longer become horrible on mobile). Or just do double newlines between the points like a normal person (;))
https://www.pastery.net/zykzva/
Though I do have a 4-line Caddy config and a Postgres server on the host.
Performance was a little slow, but that could be down to my own hardware. It was just consumer grade i5 cpu and a basic SSD, in docker.
The examples they provide are good, but you cant really provide for every different config. I wanted to use traefik, so I brought the complexity on my self.
Heres where I got too, eventually stopping my trial of Nextcloud. https://gist.github.com/francis-io/935be5679b3308f5fbc3fe1bb...
My wishlist for future effort by the devs would be:
- Fully configured via env vars (and in Collabora too). - I would rather any config or state be kept in the db. It makes backup and restore easier. Env vars could be set in the db, and any restart, has the set env vars overwrite anything in the db. I want to have confidence that I can restore a db + files and have a working service come back up. At the moment, I don't trust Nextcloud to always come back up. - Keep config separate from user files. - Focus on improving speed (which it looks like they are adressing with this post). - Focus on more app usability. I remember in portrait it being hard to use.
Overall, the software is great and I'm looking forward to the future, but to store my personal data I will need to have a little more confidence.
(I can't seem to make a bullet point list on HN)