snailmailman
today at 5:48 PM
They have an âall in oneâ container that supposedly works out of the box.
I didnât want to give it access to the docker socket, with the ability to spawn its own containers. So instead I just use the nextcloud container directly. (With several other containers, like DB, reverse proxy, collabora, etc) Itâs a mess to configure, hence their recommendation to use their âall in oneâ setup. All sorts of weird defaults with documentation that says âthis is the default but you should absolutely change it to do X instead so that it performs betterâ. Things like setting up a service to generate thumbnails, setting up redis, etc.
Once configured though, it mostly just works. You canât let it auto update between major versions, but you probably should be doing that anyway. There are usually breaking changes and you have to manually run a command or two between major updates. That doesnât happen too frequently though.
I canât speak to the quality of the all-in-one setup. Itâs likely easier than what I did - but also whatâs the point of putting it in docker and also giving it control of docker? Seems to defeat the point of containerization.