replaced PHP built-in server with the Symfony CLI one

Author: fabpot

configuration/micro_kernel_trait.rst

@@ -74,11 +74,12 @@ Next, create an ``index.php`` file that creates a kernel class and executes it::
     $response->send();
     $kernel->terminate($request, $response);
 
-That's it! To test it, you can start the built-in web server:
+That's it! To test it, start the :doc:`Symfony Local Web Server
+</setup/symfony_server>`:
 
 .. code-block:: terminal
 
-    $ php -S localhost:8000
+    $ symfony server:start
 
 Then see the JSON response in your browser:
 
@@ -335,12 +336,13 @@ this:
     ├─ composer.json
     └─ composer.lock
 
-As before you can use PHP built-in server:
+As before you can use the :doc:`Symfony Local Web Server
+</setup/symfony_server>`:
 
 .. code-block:: terminal
 
     cd web/
-    $ php -S localhost:8000
+    $ symfony server:start
 
 Then see webpage in browser:
 

create_framework/front_controller.rst

@@ -58,7 +58,7 @@ to test this code properly.
 
 Moreover, adding a new page means that we need to create a new PHP script,
 which name is exposed to the end user via the URL
-(``http://127.0.0.1:4321/bye.php``): there is a direct mapping between the PHP
+(``http://127.0.0.1:8000/bye.php``): there is a direct mapping between the PHP
 script name and the client URL. This is because the dispatching of the request
 is done by the web server directly. It might be a good idea to move this
 dispatching to our code for better flexibility. This can be achieved by routing
@@ -109,17 +109,17 @@ we return a custom 404 page; you are now in control of your website.
 
 To access a page, you must now use the ``front.php`` script:
 
-* ``http://127.0.0.1:4321/front.php/hello?name=Fabien``
+* ``http://127.0.0.1:8000/front.php/hello?name=Fabien``
 
-* ``http://127.0.0.1:4321/front.php/bye``
+* ``http://127.0.0.1:8000/front.php/bye``
 
 ``/hello`` and ``/bye`` are the page *paths*.
 
 .. tip::
 
     Most web servers like Apache or nginx are able to rewrite the incoming URLs
     and remove the front controller script so that your users will be able to
-    type ``http://127.0.0.1:4321/hello?name=Fabien``, which looks much better.
+    type ``http://127.0.0.1:8000/hello?name=Fabien``, which looks much better.
 
 The trick is the usage of the ``Request::getPathInfo()`` method which returns
 the path of the Request by removing the front controller script name including
@@ -153,12 +153,12 @@ web root directory:
 Now, configure your web server root directory to point to ``web/`` and all
 other files won't be accessible from the client anymore.
 
-To test your changes in a browser (``http://localhost:4321/hello?name=Fabien``), run
-the PHP built-in server:
+To test your changes in a browser (``http://localhost:8000/hello?name=Fabien``),
+run the :doc:`Symfony Local Web Server </setup/symfony_server>`:
 
 .. code-block:: terminal
 
-    $ php -S 127.0.0.1:4321 -t web/ web/front.php
+    $ symfony server:start --passthru=front.php
 
 .. note::
 

create_framework/introduction.rst

@@ -101,14 +101,13 @@ start with the simplest web application we can think of in PHP::
 
     printf('Hello %s', $name);
 
-You can use the PHP built-in server to test this great application in a browser
-(``http://localhost:4321/index.php?name=Fabien``):
+You can use the :doc:`Symfony Local Web Server </setup/symfony_server>` to test
+this great application in a browser
+(``http://localhost:8000/index.php?name=Fabien``):
 
 .. code-block:: terminal
 
-    $ php -S 127.0.0.1:4321
-
-Otherwise, you can always use your own server (Apache, Nginx, etc.).
+    $ symfony server:start
 
 In the :doc:`next chapter </create_framework/http_foundation>`, we are going to
 introduce the HttpFoundation Component and see what it brings us.