Merge branch '6.4' into 7.2

* 6.4:
  Tweaks and fixes
  Rename and refocus Symfony Local Web Server docs to Symfony CLI

Author: javiereguiluz

_build/redirection_map

@@ -435,6 +435,7 @@
 /setup/composer /setup
 /security/security_checker /setup
 /setup/built_in_web_server /setup/symfony_server
+/setup/symfony_server /setup/symfony_cli
 /service_container/parameters /configuration
 /routing/generate_url_javascript /routing
 /routing/slash_in_parameter /routing

configuration/micro_kernel_trait.rst

@@ -101,7 +101,7 @@ Next, create an ``index.php`` file that defines the kernel class and runs it:
         };
 
 That's it! To test it, start the :doc:`Symfony Local Web Server
-</setup/symfony_server>`:
+</setup/symfony_cli>`:
 
 .. code-block:: terminal
 
@@ -466,7 +466,7 @@ this:
     └─ composer.lock
 
 As before you can use the :doc:`Symfony Local Web Server
-</setup/symfony_server>`:
+</setup/symfony_cli>`:
 
 .. code-block:: terminal
 

console.rst

@@ -101,7 +101,7 @@ completion (by default, by pressing the Tab key).
 .. tip::
 
     If you are using the :doc:`Symfony local web server
-    </setup/symfony_server>`, it is recommended to use the built-in completion
+    </setup/symfony_cli>`, it is recommended to use the built-in completion
     script that will ensure the right PHP version and configuration are used when
     running the Console Completion. Run ``symfony completion --help`` for the
     installation instructions for your shell. The Symfony CLI will provide

contributing/code/reproducer.rst

@@ -65,7 +65,7 @@ to a route definition. Then, after creating your project:
    of controllers, actions, etc. as in your original application.
 #. Create a small controller and add your routing definition that shows the bug.
 #. Don't create or modify any other file.
-#. Install the :doc:`local web server </setup/symfony_server>` provided by Symfony
+#. Install the :doc:`local web server </setup/symfony_cli>` provided by Symfony
    and use the ``symfony server:start`` command to browse to the new route and
    see if the bug appears or not.
 #. If you can see the bug, you're done and you can already share the code with us.

create_framework/front_controller.rst

@@ -154,7 +154,7 @@ Now, configure your web server root directory to point to ``web/`` and all
 other files will no longer be accessible from the client.
 
 To test your changes in a browser (``http://localhost:4321/hello?name=Fabien``),
-run the :doc:`Symfony Local Web Server </setup/symfony_server>`:
+run the :doc:`Symfony Local Web Server </setup/symfony_cli>`:
 
 .. code-block:: terminal
 

create_framework/introduction.rst

@@ -101,7 +101,7 @@ start with the simplest web application we can think of in PHP::
 
     printf('Hello %s', $name);
 
-You can use the :doc:`Symfony Local Web Server </setup/symfony_server>` to test
+You can use the :doc:`Symfony Local Web Server </setup/symfony_cli>` to test
 this great application in a browser
 (``http://localhost:8000/index.php?name=Fabien``):
 

frontend/encore/dev-server.rst

@@ -53,7 +53,7 @@ method in your ``webpack.config.js`` file:
 Enabling HTTPS using the Symfony Web Server
 -------------------------------------------
 
-If you're using the :doc:`Symfony web server </setup/symfony_server>` locally with HTTPS,
+If you're using the :doc:`Symfony web server </setup/symfony_cli>` locally with HTTPS,
 you'll need to also tell the dev-server to use HTTPS. To do this, you can reuse the Symfony web
 server SSL certificate:
 

mailer.rst

@@ -1806,7 +1806,7 @@ Enabling an Email Catcher
 When developing locally, it is recommended to use an email catcher. If you have
 enabled Docker support via Symfony recipes, an email catcher is automatically
 configured. In addition, if you are using the :doc:`Symfony local web server
-</setup/symfony_server>`, the mailer DSN is automatically exposed via the
+</setup/symfony_cli>`, the mailer DSN is automatically exposed via the
 :ref:`symfony binary Docker integration <symfony-server-docker>`.
 
 Sending Test Emails

mercure.rst

@@ -72,7 +72,7 @@ Thanks to :doc:`the Docker integration of Symfony </setup/docker>`,
 :ref:`Flex <symfony-flex>` proposes to install a Mercure hub for development.
 Run ``docker-compose up`` to start the hub if you have chosen this option.
 
-If you use the :doc:`Symfony Local Web Server </setup/symfony_server>`,
+If you use the :doc:`Symfony Local Web Server </setup/symfony_cli>`,
 you must start it with the ``--no-tls`` option to prevent mixed content and
 invalid TLS certificate issues:
 

page_creation.rst

@@ -80,7 +80,7 @@ metadata to code):
           }
       }
 
-That's it! If you are using :doc:`the Symfony web server </setup/symfony_server>`,
+That's it! If you are using :doc:`the Symfony web server </setup/symfony_cli>`,
 try it out by going to: http://localhost:8000/lucky/number
 
 .. tip::

quick_tour/the_big_picture.rst

@@ -42,7 +42,7 @@ Symfony application:
 Can we already load the project in a browser? Yes! You can set up
 :doc:`Nginx or Apache </setup/web_server_configuration>` and configure their
 document root to be the ``public/`` directory. But, for development, it's better
-to :doc:`install the Symfony local web server </setup/symfony_server>` and run
+to :doc:`install the Symfony local web server </setup/symfony_cli>` and run
 it as follows:
 
 .. code-block:: terminal

setup.rst

@@ -121,7 +121,7 @@ development.
 .. _symfony-binary-web-server:
 
 However for local development, the most convenient way of running Symfony is by
-using the :doc:`local web server </setup/symfony_server>` provided by the
+using the :doc:`local web server </setup/symfony_cli>` provided by the
 ``symfony`` binary. This local server provides among other things support for
 HTTP/2, concurrent requests, TLS/SSL and automatic generation of security
 certificates.