app/console -> bin/console

cookbook/assetic/asset_management.rst

@@ -500,7 +500,7 @@ each time you deploy), you should run the following command:
 
 .. code-block:: bash
 
-    $ php app/console assetic:dump --env=prod --no-debug
+    $ php bin/console assetic:dump --env=prod --no-debug
 
 This will physically generate and write each file that you need (e.g. ``/js/abcd123.js``).
 If you update any of your assets, you'll need to run this again to regenerate
@@ -542,7 +542,7 @@ need to dump them manually. To do so, run the following command:
 
 .. code-block:: bash
 
-    $ php app/console assetic:dump
+    $ php bin/console assetic:dump
 
 This physically writes all of the asset files you need for your ``dev``
 environment. The big disadvantage is that you need to run this each time
@@ -551,7 +551,7 @@ assets will be regenerated automatically *as they change*:
 
 .. code-block:: bash
 
-    $ php app/console assetic:watch
+    $ php bin/console assetic:watch
 
 The ``assetic:watch`` command was introduced in AsseticBundle 2.4. In prior
 versions, you had to use the ``--watch`` option of the ``assetic:dump``

cookbook/bundles/installation.rst

@@ -108,14 +108,14 @@ via the ``config:dump-reference`` command:
 
 .. code-block:: bash
 
-    $ app/console config:dump-reference AsseticBundle
+    $ bin/console config:dump-reference AsseticBundle
 
 Instead of the full bundle name, you can also pass the short name used as the root
 of the bundle's configuration:
 
 .. code-block:: bash
 
-    $ app/console config:dump-reference assetic
+    $ bin/console config:dump-reference assetic
 
 The output will look like this:
 

cookbook/configuration/apache_router.rst

@@ -98,7 +98,7 @@ Now generate the mod_rewrite rules:
 
 .. code-block:: bash
 
-    $ php app/console router:dump-apache -e=prod --no-debug
+    $ php bin/console router:dump-apache -e=prod --no-debug
 
 Which should roughly output the following:
 

cookbook/configuration/environments.rst

@@ -221,13 +221,13 @@ behavior:
 .. code-block:: bash
 
     # 'dev' environment and debug enabled
-    $ php app/console command_name
+    $ php bin/console command_name
 
     # 'prod' environment (debug is always disabled for 'prod')
-    $ php app/console command_name --env=prod
+    $ php bin/console command_name --env=prod
 
     # 'test' environment and debug disabled
-    $ php app/console command_name --env=test --no-debug
+    $ php bin/console command_name --env=test --no-debug
 
 In addition to the ``--env`` and ``--debug`` options, the behavior of Symfony
 commands can also be controlled with environment variables. The Symfony console

cookbook/configuration/front_controllers_and_kernel.rst

@@ -75,7 +75,7 @@ as the default one.
     access. For example, you don't want to make a debugging environment
     available to arbitrary users in your production environment.
 
-Technically, the `app/console`_ script used when running Symfony on the command
+Technically, the `bin/console`_ script used when running Symfony on the command
 line is also a front controller, only that is not used for web, but for command
 line requests.
 
@@ -162,7 +162,7 @@ way of loading your configuration.
 .. _Symfony Standard Edition: https://github.com/symfony/symfony-standard
 .. _app.php: https://github.com/symfony/symfony-standard/blob/master/web/app.php
 .. _app_dev.php: https://github.com/symfony/symfony-standard/blob/master/web/app_dev.php
-.. _app/console: https://github.com/symfony/symfony-standard/blob/master/app/console
+.. _bin/console: https://github.com/symfony/symfony-standard/blob/master/bin/console
 .. _AppKernel: https://github.com/symfony/symfony-standard/blob/master/app/AppKernel.php
 .. _decorate: https://en.wikipedia.org/wiki/Decorator_pattern
 .. _RewriteRule shipped with the Symfony Standard Edition: https://github.com/symfony/symfony-standard/blob/master/web/.htaccess

cookbook/configuration/override_dir_structure.rst

@@ -154,8 +154,8 @@ file:
 
     .. code-block:: bash
 
-        $ php app/console cache:clear --env=prod
-        $ php app/console assetic:dump --env=prod --no-debug
+        $ php bin/console cache:clear --env=prod
+        $ php bin/console assetic:dump --env=prod --no-debug
 
 Override the ``vendor`` Directory
 ---------------------------------

cookbook/console/console_command.rst

@@ -68,7 +68,7 @@ This command will now automatically be available to run:
 
 .. code-block:: bash
 
-    $ php app/console demo:greet Fabien
+    $ php bin/console demo:greet Fabien
 
 .. _cookbook-console-dic:
 

cookbook/console/usage.rst

@@ -17,18 +17,18 @@ clear and warm the ``prod`` cache you need to run:
 
 .. code-block:: bash
 
-    $ php app/console cache:clear --env=prod
+    $ php bin/console cache:clear --env=prod
 
 or the equivalent:
 
 .. code-block:: bash
 
-    $ php app/console cache:clear -e prod
+    $ php bin/console cache:clear -e prod
 
 In addition to changing the environment, you can also choose to disable debug mode.
 This can be useful where you want to run commands in the ``dev`` environment
 but avoid the performance hit of collecting debug data:
 
 .. code-block:: bash
 
-    $ php app/console list --no-debug
+    $ php bin/console list --no-debug

cookbook/deployment/azure-website.rst

@@ -388,7 +388,7 @@ MySQL database.
 
 .. code-block:: bash
 
-    $ php app/console doctrine:schema:update --force
+    $ php bin/console doctrine:schema:update --force
 
 This command builds the tables and indexes for your MySQL database. If your
 Symfony application is more complex than a basic Symfony Standard Edition, you

cookbook/deployment/heroku.rst

@@ -275,7 +275,7 @@ This is also very useful to build assets on the production system, e.g. with Ass
     {
         "scripts": {
             "compile": [
-                "app/console assetic:dump"
+                "bin/console assetic:dump"
             ]
         }
     }

cookbook/deployment/platformsh.rst

@@ -69,9 +69,9 @@ Platform.sh how to deploy your application (read more about
     hooks:
         build: |
           rm web/app_dev.php
-          app/console --env=prod assetic:dump --no-debug
+          bin/console --env=prod assetic:dump --no-debug
         deploy: |
-          app/console --env=prod cache:clear
+          bin/console --env=prod cache:clear
 
 For best practices, you should also add a ``.platform`` folder at the root of
 your Git repository which contains the following files:

cookbook/deployment/tools.rst

@@ -150,7 +150,7 @@ Make sure you clear (and warm-up) your Symfony cache:
 
 .. code-block:: bash
 
-    $ php app/console cache:clear --env=prod --no-debug
+    $ php bin/console cache:clear --env=prod --no-debug
 
 E) Dump your Assetic Assets
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -159,7 +159,7 @@ If you're using Assetic, you'll also want to dump your assets:
 
 .. code-block:: bash
 
-    $ php app/console assetic:dump --env=prod --no-debug
+    $ php bin/console assetic:dump --env=prod --no-debug
 
 F) Other Things!
 ~~~~~~~~~~~~~~~~

cookbook/doctrine/console.rst

@@ -11,7 +11,7 @@ command:
 
 .. code-block:: bash
 
-    $ php app/console list doctrine
+    $ php bin/console list doctrine
 
 A list of available commands will print out. You can find out more information
 about any of these commands (or any Symfony command) by running the ``help``
@@ -20,7 +20,7 @@ task, run:
 
 .. code-block:: bash
 
-    $ php app/console help doctrine:database:create
+    $ php bin/console help doctrine:database:create
 
 Some notable or interesting tasks include:
 
@@ -30,7 +30,7 @@ Some notable or interesting tasks include:
 
   .. code-block:: bash
 
-      $ php app/console doctrine:ensure-production-settings --env=prod
+      $ php bin/console doctrine:ensure-production-settings --env=prod
 
 * ``doctrine:mapping:import`` - allows Doctrine to introspect an existing
   database and create mapping information. For more information, see

cookbook/doctrine/multiple_entity_managers.rst

@@ -165,20 +165,20 @@ When working with multiple connections to create your databases:
 .. code-block:: bash
 
     # Play only with "default" connection
-    $ php app/console doctrine:database:create
+    $ php bin/console doctrine:database:create
 
     # Play only with "customer" connection
-    $ php app/console doctrine:database:create --connection=customer
+    $ php bin/console doctrine:database:create --connection=customer
 
 When working with multiple entity managers to update your schema:
 
 .. code-block:: bash
 
     # Play only with "default" mappings
-    $ php app/console doctrine:schema:update --force
+    $ php bin/console doctrine:schema:update --force
 
     # Play only with "customer" mappings
-    $ php app/console doctrine:schema:update --force --em=customer
+    $ php bin/console doctrine:schema:update --force --em=customer
 
 If you *do* omit the entity manager's name when asking for it,
 the default entity manager (i.e. ``default``) is returned::

cookbook/doctrine/registration_form.rst

@@ -322,7 +322,7 @@ database schema using this command:
 
 .. code-block:: bash
 
-   $ php app/console doctrine:schema:update --force
+   $ php bin/console doctrine:schema:update --force
 
 That's it! Head to ``/register`` to try things out!
 

cookbook/doctrine/reverse_engineering.rst

@@ -59,7 +59,7 @@ table fields.
 
 .. code-block:: bash
 
-    $ php app/console doctrine:mapping:import --force AcmeBlogBundle xml
+    $ php bin/console doctrine:mapping:import --force AcmeBlogBundle xml
 
 This command line tool asks Doctrine to introspect the database and generate
 the XML metadata files under the ``src/Acme/BlogBundle/Resources/config/doctrine``
@@ -92,8 +92,8 @@ entity classes by executing the following two commands.
 
 .. code-block:: bash
 
-    $ php app/console doctrine:mapping:convert annotation ./src
-    $ php app/console doctrine:generate:entities AcmeBlogBundle
+    $ php bin/console doctrine:mapping:convert annotation ./src
+    $ php bin/console doctrine:generate:entities AcmeBlogBundle
 
 The first command generates entity classes with annotation mappings. But
 if you want to use YAML or XML mapping instead of annotations, you should

cookbook/email/spool.rst

@@ -117,19 +117,19 @@ There is a console command to send the messages in the spool:
 
 .. code-block:: bash
 
-    $ php app/console swiftmailer:spool:send --env=prod
+    $ php bin/console swiftmailer:spool:send --env=prod
 
 It has an option to limit the number of messages to be sent:
 
 .. code-block:: bash
 
-    $ php app/console swiftmailer:spool:send --message-limit=10 --env=prod
+    $ php bin/console swiftmailer:spool:send --message-limit=10 --env=prod
 
 You can also set the time limit in seconds:
 
 .. code-block:: bash
 
-    $ php app/console swiftmailer:spool:send --time-limit=10 --env=prod
+    $ php bin/console swiftmailer:spool:send --time-limit=10 --env=prod
 
 Of course you will not want to run this manually in reality. Instead, the
 console command should be triggered by a cron job or scheduled task and run

cookbook/event_dispatcher/event_listener.rst

@@ -274,11 +274,11 @@ using the console. To show all events and their listeners, run:
 
 .. code-block:: bash
 
-    $ php app/console debug:event-dispatcher
+    $ php bin/console debug:event-dispatcher
 
 You can get registered listeners for a particular event by specifying
 its name:
 
 .. code-block:: bash
 
-    $ php app/console debug:event-dispatcher kernel.exception
+    $ php bin/console debug:event-dispatcher kernel.exception

cookbook/profiler/profiling_data.rst

@@ -53,10 +53,10 @@ one where the information was generated, use the ``profiler:export`` and
 .. code-block:: bash
 
     # on the production machine
-    $ php app/console profiler:export > profile.data
+    $ php bin/console profiler:export > profile.data
 
     # on the development machine
-    $ php app/console profiler:import /path/to/profile.data
+    $ php bin/console profiler:import /path/to/profile.data
 
     # you can also pipe from the STDIN
-    $ cat /path/to/profile.data | php app/console profiler:import
+    $ cat /path/to/profile.data | php bin/console profiler:import

cookbook/security/acl.rst

@@ -96,7 +96,7 @@ Fortunately, there is a task for this. Simply run the following command:
 
 .. code-block:: bash
 
-    $ php app/console init:acl
+    $ php bin/console init:acl
 
 Getting Started
 ---------------

cookbook/security/entity_provider.rst

@@ -145,13 +145,13 @@ by running:
 
 .. code-block:: bash
 
-    $ php app/console doctrine:generate:entities AppBundle/Entity/User
+    $ php bin/console doctrine:generate:entities AppBundle/Entity/User
 
 Next, make sure to :ref:`create the database table <book-doctrine-creating-the-database-tables-schema>`:
 
 .. code-block:: bash
 
-    $ php app/console doctrine:schema:update --force
+    $ php bin/console doctrine:schema:update --force
 
 What's this UserInterface?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~