Symfony
a SensioLabs product
DOWNLOAD NOW

Table of Contents

Creative Commons License
This work is licensed under a
Creative Commons
Attribution-Share Alike 3.0
Unported License.

Master Symfony2 fundamentals

Be trained by SensioLabs experts (2 to 6 day sessions -- French or English).
trainings.sensiolabs.com

Symfony hosting done right

ServerGrove, outstanding support at the right price for your Symfony hosting needs.
servergrove.com

Discover the SensioLabs Support

Access to the SensioLabs Competency Center for an exclusive and tailor-made support on Symfony
sensiolabs.com
Home » Documentation » The Cookbook » Configuration » How to override Symfony's Default Directory Structure
2.3 version

How to override Symfony's Default Directory Structure

How to override Symfony's Default Directory Structure

Symfony automatically ships with a default directory structure. You can easily override this directory structure to create your own. The default directory structure is:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
app/
    cache/
    config/
    logs/
    ...
src/
    ...
vendor/
    ...
web/
    app.php
    ...

Override the cache directory

You can override the cache directory by overriding the getCacheDir method in the AppKernel class of you application:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
// app/AppKernel.php

// ...
class AppKernel extends Kernel
{
    // ...

    public function getCacheDir()
    {
        return $this->rootDir.'/'.$this->environment.'/cache';
    }
}

$this->rootDir is the absolute path to the app directory and $this->environment is the current environment (i.e. dev). In this case you have changed the location of the cache directory to app/{environment}/cache.

Caution

You should keep the cache directory different for each environment, otherwise some unexpected behaviour may happen. Each environment generates its own cached config files, and so each needs its own directory to store those cache files.

Override the logs directory

Overriding the logs directory is the same as overriding the cache directory, the only difference is that you need to override the getLogDir method:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
// app/AppKernel.php

// ...
class AppKernel extends Kernel
{
    // ...

    public function getLogDir()
    {
        return $this->rootDir.'/'.$this->environment.'/logs';
    }
}

Here you have changed the location of the directory to app/{environment}/logs.

Override the web directory

If you need to rename or move your web directory, the only thing you need to guarantee is that the path to the app directory is still correct in your app.php and app_dev.php front controllers. If you simply renamed the directory, you're fine. But if you moved it in some way, you may need to modify the paths inside these files:

1
2
require_once __DIR__.'/../Symfony/app/bootstrap.php.cache';
require_once __DIR__.'/../Symfony/app/AppKernel.php';

Since Symfony 2.1 (in which Composer is introduced), you also need to change the extra.symfony-web-dir option in the composer.json file:

{
    ...
    "extra": {
        ...
        "symfony-web-dir": "my_new_web_dir"
    }
}

Tip

Some shared hosts have a public_html web directory root. Renaming your web directory from web to public_html is one way to make your Symfony project work on your shared host. Another way is to deploy your application to a directory outside of your web root, delete your public_html directory, and then replace it with a symbolic link to the web in your project.

Note

If you use the AsseticBundle you need to configure this, so it can use the correct web directory:

  • YAML
    1
2
3
4
5
6
    # app/config/config.yml

# ...
assetic:
    # ...
    read_from: "%kernel.root_dir%/../../public_html"
  • XML
    1
2
3
4
    <!-- app/config/config.xml -->

<!-- ... -->
<assetic:config read-from="%kernel.root_dir%/../../public_html" />
  • PHP
    1
2
3
4
5
6
7
    // app/config/config.php

// ...
$container->loadFromExtension('assetic', array(
    // ...
    'read_from' => '%kernel.root_dir%/../../public_html',
));

Now you just need to dump the assets again and your application should work:

1
$ php app/console assetic:dump --env=prod --no-debug
« How to Master and Create new Environments | Understanding how the Front Controller, Kernel and Environments work together »

NEWS FROM THE BLOG

Visit Symfony's blog

IN THE NEWS

Announcing the next Symfony Live Conference 2013 in Portland

UPCOMING TRAINING SESSIONS

View all sessions

sf - Symfony is a trademark of Fabien Potencier. All rights reserved.

What is Symfony?

Get Started

Learn Symfony

Marketplace

Community

Services

Blog

About