mirror of
https://github.com/nextcloud/all-in-one.git
synced 2025-02-23 05:15:34 +08:00
Merge pull request #853 from nextcloud/enh/noid/requirements
add a list of requirements for integrating new containers
This commit is contained in:
commit
85caab7507
1 changed files with 10 additions and 0 deletions
10
readme.md
10
readme.md
|
@ -407,3 +407,13 @@ It is possible to install any of these to get a GUI for your AIO database. The p
|
|||
|
||||
### How to migrate from an already existing Nextcloud installation to Nextcloud AIO?
|
||||
Please see the following documentation on this: [migration.md](https://github.com/nextcloud/all-in-one/blob/main/migration.md)
|
||||
|
||||
### Requirements for integrating new containers
|
||||
For integrating new containers, they must pass specific requirements for being considered to get integrated in AIO itself. Even if not considered, we may add some documentation on it.
|
||||
|
||||
What are the requirements?
|
||||
1. New containers must be related to Nextcloud. Related means that there must be a feature in Nextcloud that gets added by adding this container.
|
||||
2. It must be optionally installable. Disabling and enabling the container from the AIO interface must work and must not produce any unexpected side-effects.
|
||||
3. The feature that gets added into Nextcloud by adding the container must be maintained by the Nextcloud GmbH.
|
||||
4. It must be possible to run the container without big quirks inside docker containers. Big quirks means e.g. needing to change the capabilities or security options.
|
||||
5. The container should not mount directories from the host into the container: only docker volumes should be used.
|
||||
|
|
Loading…
Reference in a new issue