From 9f57b3a272153dc1b72512a34e1ff71f6f3c184a Mon Sep 17 00:00:00 2001 From: Christian Manivong Date: Thu, 8 Oct 2026 14:02:44 +0200 Subject: [PATCH] docs: a target server needs at least 4 GB of RAM The requirements named Docker and the .env but no size. netOrk's own containers take about 2.4 GB on a test server with 74 devices, and at least 0.9 GB stayed free once netOrk#752 was fixed. Less than 4 GB leaves no room for a large task. The breakdown per container lives in netOrk's docs/TECHNICAL_DESIGN.md, "Worker memory". --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index 20e4e1c..8edd547 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,9 @@ start, and database migrations run from that same image. - `ssh` with key-based access to every target **On every target server:** +- at least 4 GB of RAM. On a test server with 74 devices, netOrk's containers took about + 2.4 GB, and at least 0.9 GB stayed free. A large task needs that room. The breakdown + per container is in netOrk's `docs/TECHNICAL_DESIGN.md`, "Worker memory". - Docker with the compose plugin - a directory `~/netork/` with netOrk's `.env`, which holds the database and application settings the compose file reads (`env_file: .env`)