Merge branch '4.4' into 5.1

* 4.4:
  Add warning on Docker integration
  Fix: Add line breaks
  Fix: Typo
  [Cache] Adds mention of using FileSystemTagAwareAdatpter

Author: OskarStark

components/cache/adapters/filesystem_adapter.rst

@@ -55,5 +55,22 @@ and cache root path as constructor parameters::
     :ref:`pruning of expired cache items <component-cache-cache-pool-prune>` by
     calling its ``prune()`` method.
 
+
+.. _filesystem-tag-aware-adapter:
+
+Working with Tags
+-----------------
+
+In order to use tag-based invalidation, you can wrap your adapter in
+:class:`Symfony\\Component\\Cache\\Adapter\\TagAwareAdapter`, but it's often
+more interesting to use the dedicated :class:`Symfony\\Component\\Cache\\Adapter\\FilesystemTagAwareAdapter`.
+Since tag invalidation logic is implemented using links on filesystem, this
+adapter offers better read performance when using tag-based invalidation::
+
+    use Symfony\Component\Cache\Adapter\FilesystemTagAwareAdapter;
+
+    $cache = new FilesystemTagAwareAdapter();
+
+
 .. _`tmpfs`: https://wiki.archlinux.org/index.php/tmpfs
 .. _`RAM disk solutions`: https://en.wikipedia.org/wiki/List_of_RAM_drive_software

components/cache/cache_invalidation.rst

@@ -61,7 +61,8 @@ method.
 .. note::
 
     When using a Redis backend, consider using :ref:`RedisTagAwareAdapter <redis-tag-aware-adapter>`
-    which is optimized for this purpose.
+    which is optimized for this purpose. When using filesystem, likewise consider to use
+    :ref:`FilesystemTagAwareAdapter <filesystem-tag-aware-adapter>`.
 
 The :class:`Symfony\\Component\\Cache\\Adapter\\TagAwareAdapter` class implements
 instantaneous invalidation (time complexity is ``O(N)`` where ``N`` is the number

setup/symfony_server.rst

@@ -378,6 +378,16 @@ its location, same as for ``docker-compose``:
     If you have more than one Docker Compose file, you can provide them all
     separated by ``:`` as explained in the `Docker compose CLI env var reference`_.
 
+.. caution::
+
+    When using Symfony binary with ``php bin/console`` (``symfony console ...``)
+    the binay will **always** use environment variables detected via Docker and will
+    ignore local environment variables.
+    For example if you set up a different database name in your ``.env.test`` file
+    (``DATABASE_URL=mysql://db_user:db_password@127.0.0.1:3306/test``) and if you run
+    ``symfony console doctrine:database:drop --force --env=test`` the command will drop the database
+    defined in your Docker configuration and not the "test" one.
+
 SymfonyCloud Integration
 ------------------------