Simon L.
cd61f66467
## Summary - Integrates Desec into the AIO interface which simplifies the domain registration and domain setup. - You can either create a new account directly or use an existing account. - You have a button that you can open where the process will be done. After the process is done, the whole page reloads and you can continue with the setup. - Caddy and dnsmasq community containers will be activated during the process which will take over the cert generation and enable split-brain dns. - Community containers will work automatically for example Vaultwarden as the subdomains of the desec domain point automatically via a wildcard dns entry towards the main desec domain. - Playwright tests are added to ensure that the system works as expected in the future - the desec api is mocked via a small node js based file. - the qa and other docs were updated to mention desec
Nextcloud All-in-One mastercontainer
This folder contains the OCI/Docker container definition, along with associated resources and
configuration files, for building the mastercontainer as part of the Nextcloud All-in-One
project. This container hosts the Nextcloud AIO interface1 , and a dedicated PHP environment
for it (which is completely independent of the Nextcloud Server).
Overview
The mastercontainer acts as the central orchestration service for the deployment and management of all other containers in the Nextcloud All-in-One stack. It hosts:
- A dedicated PHP SAPI/backend (php-fpm) for AIO itself (not Nextcloud Server)
- A Caddy server enabling self-signed HTTPS access to the AIO frontend on port 8080/tcp.
- A Caddy server enabling trusted HTTPS access to the AIO frontend on port 8443/tcp.
- Caddy will automatically issue a Let's Encrypt issued certificate if port 80 and 8443
is open/forwarded and a domain pointer is in place; then, simply open the Nextcloud AIO interface using the
domain (
https://your-domain-that-points-to-this-server.tld:8443). The Let's Encrypt certificate request will use an ACME HTTP-01 challenge.
- Caddy will automatically issue a Let's Encrypt issued certificate if port 80 and 8443
is open/forwarded and a domain pointer is in place; then, simply open the Nextcloud AIO interface using the
domain (
- Miscellaneous support services specific to AIO (backup management, health checks, etc.)
Key Responsibilities
- Orchestrates the deployment and lifecycle of all Nextcloud service containers
- Handles initial setup and container configuration
- Coordinates image updates
- Monitors general system health
It triggers the initial installation and ensures the smooth operation of the Nextcloud All-in-One stack.
Contents
- Dockerfile: Instructions for building the mastercontainer image.
- Entrypoint script: The
start.shscript is used for container initialization and runtime configuration before starting supervisord. - Nextcloud All-in-One Controller App: The core AIO orchestrator that handles configuration and settings for the containers.
- Supervisor: The
supervisord.conffile defines the long-running services hosted within the container (php-fpm, cron, etc.)
Usage
This container should be used as the trigger image when deploying the Nextcloud All-in-One stack in a Docker or other OCI-compliant container environment. For detailed deployment instructions, refer to the project documentation.
Related Resources
Contributing
Contributions are welcome! Please follow the Nextcloud project's guidelines and submit pull requests or issues via the main repository.
License
This folder and its contents are licensed under the GNU AGPLv3, in line with the rest of Nextcloud All-in-One.
-
The Nextcloud All-in-One interface allows users to install, configure, and manage their Nextcloud instance and related containers via a secure web interface and API. It automates and simplifies complex tasks such as container orchestration, backups, updates, and service management for users deploying Nextcloud in Docker environments. ↩︎