Nextcloud
Nextcloud: a first setup, important settings, verification, and recovery considerations.
Working directory: ~/homelab/apps/cloud. Follow the common setup workflow first. This is a setup note based on the linked documentation, not a copy of my live configuration or a runtime verification of this full stack.
Start here
Nextcloud stores files and offers collaboration features. Start with the official Compose example for the selected release, its supported database, and Redis where required by that example. Add office integration only after file upload and recovery work. A Nextcloud container alone is not the complete deployment.
Settings and data
Persist application configuration, uploaded data, and database storage. Use the documented background-job mechanism, rather than relying on someone visiting the page. Set trusted domains and trusted proxies to the actual entry points of your own deployment, not a wildcard accepting everything.
Check it
Upload a disposable text file, download it, compare its contents, and confirm it survives recreation of the application container. Check the administration overview for background-job and configuration warnings. Then test a supported backup and restore into a separate instance.
When something fails
Redirect loops usually call for checking the public URL and proxy headers. Upload failures need size limits, disk space, permissions, and logs checked at both proxy and app. Back up database and files consistently; never attempt a major-version rollback by changing only the image tag.