-
Notifications
You must be signed in to change notification settings - Fork 896
-
Hello,
I've read #359 and https://github.com/nextcloud/all-in-one/blob/main/multiple-instances.md, but this is not the way I see multiple instances.
If I don't run AIO, I can run multiple nextcloud in multiple containers on the same engine. I just need to change the container names, exposed ports, or better, use my reverse proxy to access each nextcloud using a different name.
In the AIO case, as the deployed containers will be with the same name / networks & so on, this is not doable.
Could it be simply done by adding a environment variable such as "installation_prefix", which would be added before the container names / networks created by the AIO installer ?
That way we could simply run multiple AIO instances on the same docker engine without the need for users, VMs or anything fancy.
I also posted here, not being sure where this question / idea best resides : https://help.nextcloud.com/t/nextcloud-aio-containers-name-prefix/230667
Beta Was this translation helpful? Give feedback.
All reactions
Hi, this is in theory doable but it requires a refactoring of almost the whole project. So I see only little benefit over the documented way compared to the added complexity.
Or in other words: I will not work on this.
FYI: you might be able to make it work with https://github.com/nextcloud/all-in-one/tree/main/manual-install. See https://github.com/nextcloud/all-in-one/blob/main/manual-install/latest.yml
Replies: 1 comment 1 reply
-
Hi, this is in theory doable but it requires a refactoring of almost the whole project. So I see only little benefit over the documented way compared to the added complexity.
Or in other words: I will not work on this.
FYI: you might be able to make it work with https://github.com/nextcloud/all-in-one/tree/main/manual-install. See https://github.com/nextcloud/all-in-one/blob/main/manual-install/latest.yml
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Hallo @szaimen,
AIO ist an sich eine richtig gute Sache, weswegen ich froh bin mich endlich darauf stürzen zu können. Nach Lesen der Doku zu rootless und multi-instances stehe ich jetzt aber etwas ratlos da. Aus meiner Sicht widerspricht die Art wie AIO funktioniert im weiteren Sinne einem der Versprechen, das Docker uns macht: Laufzeitumgebungen unabhängig vom Hostsystem.
Ich habe in meinem Fall drei Optionen:
- Container auf rootless migrieren (2x NC, Traefik, Kuma, Authentik, ...), ohne zu wissen, ob alle Images mitmachen
- Weiterer VPS für jede NC-Instanz
- manual-install, die Doku rät ja aber quasi davon ab
Ich erwarte nicht, dass für mich das große Refactoring gestartet wird, aber vielleicht mal als Input für die Zukunft mitnehmen. :-)
Translation
AIO is, in itself, a really good thing, and I’m glad I can finally dive into it. However, after reading the documentation on rootless and multi-instances, I’m now a bit at a loss. From my perspective, the way AIO works fundamentally contradicts one of Docker’s core promises: runtime environments independent of the host system.
In my case, I have three options:
- Migrate containers to rootless (×ばつ NC, Traefik, Kuma, Authentik, ...), without knowing whether all images will cooperate
- Get an additional VPS for each NC instance
- Go for a manual install, though the documentation practically advises against it
I don’t expect a major refactoring to be started just for me, but maybe take this as some input for the future.
Beta Was this translation helpful? Give feedback.