From 7b614e6bc0a5e1c7293ac37b6cc76e3914b99035 Mon Sep 17 00:00:00 2001 From: blek Date: Fri, 27 Oct 2023 21:11:36 +1000 Subject: [PATCH] add note about extensive configuration --- DEPLOYING.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/DEPLOYING.md b/DEPLOYING.md index a4bcebc..877e665 100644 --- a/DEPLOYING.md +++ b/DEPLOYING.md @@ -13,6 +13,17 @@ To deploy a basic instance for general public use, follow these simple steps: 6. Create and start containers with `docker-compose up -d` 7. Route your top level reverse proxy to the `caddy` service or to the port that you opened via the docker compose file. +## More extensive configuration +Well, generally, time-wise, it is not really a good idea to create a custom services configuration. +However, I will guide you through the basic minimal configuration. + +Basically, the most minimal blek!File is a fileD service connected to a redis database. +I think that if you are clinically insance, you can set these up as a systemd services or a `screen`ed program. + +However, its not really recommended to run this without janitorD as unused files will just clog up your filesystem. +The two requirements for janitorD are to have access to the fileD's usercontent directory and the Redis database. +The default docker configuration mounts `/opt/user_content` to the same volume for both fileD and janitorD. + ## FileD configuration Unless you are running in some kind of super customized docker compose environment, just copying the `.env.example` to `.env` should be enough to get it to run.