Skip to content

init:bundle => bundle:init #125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

init:bundle => bundle:init #125

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions book/page_creation.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -400,12 +400,12 @@ each of these directories in later chapters.
or ``require`` statements. Instead, Symfony2 uses the namespace of a class
to determine its location and automatically includes the file on your
behalf the instance you need a class::

$loader->registerNamespaces(array(
'Sensio' => __DIR__.'/../src',
// ...
));

With this configuration, Symfony2 will look inside the ``src`` directory
for any class in the ``Sensio`` namespace. For autoloading to work,
the class name and path to the file must follow the same pattern:
Expand Down Expand Up @@ -543,7 +543,7 @@ And while it doesn't do anything yet, ``MyBundle`` is now ready to be used.
And as easy as this is, Symfony also provides a command-line interface for
generating a basic bundle skeleton::

./app/console init:bundle "Sensio\MyBundle" src
./app/console bundle:init "Sensio\MyBundle" src

The bundle skeleton generates with a basic controller, template and routing
resource that can be customized. We'll talk more about Symfony2's command-line
Expand Down Expand Up @@ -716,9 +716,9 @@ call the ``prod`` front controller instead::

If you open the ``web/app.php`` file, you'll that it's configured explicitly
to use the ``prod`` environment::

$kernel = new AppCache(new AppKernel('prod', false));

You can create a new front controller for a new environment by copying
this file and changing ``prod`` to some other value.

Expand Down
4 changes: 2 additions & 2 deletions book/security/acl.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,15 +63,15 @@ First, we need to configure the connection the ACL system is supposed to use:
The ACL system requires at least one Doctrine DBAL connection to be
configured. However, that does not mean that you have to use Doctrine for
mapping your domain objects. You can use whatever mapper you like for your
objects, be it Doctrine ORM, Mongo ODM, Propel, or raw SQL, the choice is
objects, be it Doctrine ORM, Mongo ODM, Propel, or raw SQL, the choice is
yours.

After the connection is configured, we have to import the database structure.
Fortunately, we have a task for this. Simply run the following command:

.. code-block:: text

php app/console init:acl
php app/console acl:init

Getting Started
---------------
Expand Down