Skip to content

Commit 74c6252

Browse files
committed
minor #11098 Some cache files might be written in runtime (cvdwel)
This PR was submitted for the master branch but it was merged into the 4.2 branch instead (closes #11098). Discussion ---------- Some cache files might be written in runtime <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/roadmap for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `master` for features of unreleased versions). --> Commits ------- 3fcb22c Some cache files might be written in runtime
2 parents 5ca3d1d + 3fcb22c commit 74c6252

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

setup/file_permissions.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,9 @@ was writable. But that is no longer true! In Symfony 4, everything works automat
99

1010
* In the ``prod`` environment (i.e. when ``APP_ENV`` is ``prod`` and ``APP_DEBUG``
1111
is ``0``), as long as you run ``php bin/console cache:warmup``, no cache files
12-
will need to be written to disk at runtime.
12+
will need to be written to disk at runtime. An exception to this is any type of
13+
runtime cache, for example a query result cache or DoctrineCacheBundle with a
14+
file_system cache provider configured.
1315

1416
* In all environments, the log directory (``var/log/`` by default) must exist
1517
and be writable by your web server user and terminal user. One way this can

0 commit comments

Comments
 (0)