[GH-ISSUE #133] Nextcloud AIO template is not really AIO #12568

Open
opened 2026-06-15 12:30:34 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @francoisWeber on GitHub (May 13, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/133

According to this line
https://github.com/Dokploy/templates/blob/main/blueprints/nextcloud-aio/docker-compose.yml#L3C5-L3C28
in the NC AIO docker compose, the image used is nextcloud:30.0.2. However, the real All-In-One image should be based on https://github.com/nextcloud/all-in-one which is quite different. IMHO it's really confusing because the tooling provided by AIO is not installed in this template.

I would suggest renaming this template into "nextcloud" and provide another template for "nextcloud AIO"

Originally created by @francoisWeber on GitHub (May 13, 2025). Original GitHub issue: https://github.com/Dokploy/templates/issues/133 According to this line https://github.com/Dokploy/templates/blob/main/blueprints/nextcloud-aio/docker-compose.yml#L3C5-L3C28 in the NC AIO docker compose, the image used is `nextcloud:30.0.2`. However, the real All-In-One image should be based on https://github.com/nextcloud/all-in-one which is quite different. IMHO it's really confusing because the tooling provided by AIO is not installed in this template. I would suggest renaming this template into "nextcloud" and provide another template for "nextcloud AIO"
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#12568