From 75c54515464f6f112f1fe785509d1a220eaaaf66 Mon Sep 17 00:00:00 2001 From: AbdBarho Date: Sun, 25 Jun 2023 11:44:36 +0200 Subject: [PATCH] Updated Usage (markdown) --- Usage.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Usage.md b/Usage.md index e91622d..ab968a5 100644 --- a/Usage.md +++ b/Usage.md @@ -37,9 +37,10 @@ put your scripts `data/config/auto/scripts` and restart the container You can use the UI to install extensions, or, you can put your extensions in `data/config/auto/extensions`. +Different extensions require additional dependencies. Some of them might conflict with each other and changing versions of packages could break things. This container will try to install missing extension dependencies on startup, but it won't resolve any problems for you. + There is also the option to create a script `data/config/auto/startup.sh` which will be called on container startup, in case you want to install any additional dependencies for your extensions or anything else. -Different extensions require additional dependencies. Some of them might conflict with each other and changing versions of packages could break things. Use the `startup.sh` script to install and guarantee the needed dependencies (`pip`, `apt`, and any others). In case something goes wrong with some dependency (as it is usually the case, unfortunately) you can always comment section in `startup.sh` file, remove the extension, and do `docker compose --profile auto down` to clean up messy containers. When run again, you will have a fresh container.