From 51556b3bac6421148e83a23cc0583ff1213c5c3a Mon Sep 17 00:00:00 2001 From: Val Lorentz Date: Sun, 9 Jul 2023 14:42:02 +0200 Subject: [PATCH] README: Document that read-only filesystem do no prevent booting This was changed in 2d40bd35d42aa262c3c2c479cfc789d0bf172d12. --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fc0b31b..fd05d49 100644 --- a/README.md +++ b/README.md @@ -30,8 +30,9 @@ require 'bootsnap/setup' ``` Note that bootsnap writes to `tmp/cache` (or the path specified by `ENV['BOOTSNAP_CACHE_DIR']`), -and that directory *must* be writable. Rails will fail to -boot if it is not. If this is unacceptable (e.g. you are running in a read-only container and +and that directory *must* be writable. Rails will fail to boot if it is not; unless the whole +filesystem is read-only (for example because of containerization/sandboxing). +If this is unacceptable (e.g. you are running in a read-only container and unwilling to mount in a writable tmpdir), you should remove this line or wrap it in a conditional. **Note also that bootsnap will never clean up its own cache: this is left up to you. Depending on your