From abc83d4e26db27abbe3a1a5b82c23b482cc3684c Mon Sep 17 00:00:00 2001 From: Patrick Dowler Date: Tue, 5 Mar 2024 15:17:37 -0800 Subject: [PATCH] Update cavern/README.md Co-authored-by: Adrian --- cavern/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cavern/README.md b/cavern/README.md index d823ad71..8e3e7cb3 100644 --- a/cavern/README.md +++ b/cavern/README.md @@ -84,7 +84,7 @@ allocation (they can read/write/delete anything) so the owner cannot be blocked within their allocation. This probably only matters for multi-user projects. Multiple _allocationParent_(s) may be configured to organise the top level of the content (e.g. /home and /projects). Paths configured to be _allocationParent_(s) will be automatically created (if necessary), owned by the _rootOwner_, and will be -anonymously readable (public). Limitation: only a single level of top-level _allocationParent_(s) are supported. +anonymously readable (public). Limitation: only top-level container nodes can be configured as _allocationParent_(s). The _filesystem.baseDir_ is the path to a base directory containing the `cavern` nodes/files.