nextcloud
Installing/enabling apps during build time or via entrypoint
Posting this as its own issue instead of a comment I made on a closed PR.
@skjnldsv Any word on the official Nextcloud best practice for doing this?
From several GitHub issues and pull requests for installing/enabling apps from a derived Dockerimage, and following the Nextcloud example docker-compose setup for alpine with nginx-proxy and LE/ACME Companion, I went ahead and followed the custom entrypoint script found here from FUSS: https://gitlab.fuss.bz.it/fuss-team/fuss-nc/-/blob/476791f41dad509c677fc25e266a072074349c0e/nextcloud-fuss/configure-fuss.sh
When I run docker-compose up, the Nextcloud container just errors out on all calls to app:install telling me that Nextcloud is not installed. Am I missing something here? Do I still have to manually create a user from the Web UI, or can I do all this via Dockerfile / entrypoint.sh and docker-compose? We really need a fully automated CLI/API way of provisioning, theming, and setting up new Nextcloud instances for new users of our service, with no work required by the end-user.
