Congratulations! You have successfully created your symfony project.

Project setup successful

This project uses the symfony libraries. If you see no image in this page, you may need to configure your web server so that it gains access to the symfony_data/web/sf/ directory.

The proper configuration of the web server seems to be the most troublesome part of Symfony installation. But fortunately there are several quick ways to solve that problem. This short guide will describe three of them from the perspective of an Apache web server user.

I’m assuming that you have Symfony already properly installed (if not – the installation guide is here). I’m working on a WAMP installation of Apache+MySQL+PHP, so the directory paths in my examples will reflect that (but the guide should work for any Apache based configuration).

Method 1 – setting a virtual host

This is the most recommended method of setting up your working environment (in fact it is the only real method out there – the other described below are just workarounds ) – you should always create a virtual host for every application. This guide will teach you how to configure your web server to cope with one project (a multi-application vhost example is coming up soon ).

First – find your apache config directory (in my WAMP install it’s C:\wamp\bin\apache\apache2.2.6\conf\) and open the httpd-vhosts.conf (which is in the sub-directory extra – C:\wamp\bin\apache\apache2.2.6\conf\extra). Delete or comment out all the lines (by adding ‘#’ at the beginning of each one) if you’re not sure what they do (if you haven’t written them they are probably just examples of vhost configuration).

In Symfony 1.2 (1.1 also?) a sample vhost config file is created automatically for every project you generate. It can be found in config/vhost.sample – feel free to copy/paste that code instead of the below example.

Now add at the end of the file your virtual host config which should look similar to this (it’s just one of possible ways of configuring  a vhost – you may find other configurations that achieve the same thing but look different – they all are correct as long as they work, right? ):

NameVirtualHost *:80

Listen 127.0.0.2:80

<VirtualHost 127.0.0.2:80>

ServerName your_application_name
DocumentRoot “c:\wamp\www\your_project\web”
DirectoryIndex index.php

<Directory “c:\wamp\www\your_project\web”>

AllowOverride All
Allow from All

</Directory>

Alias /sf “c:\wamp\bin\php\php5.2.5\PEAR\data\symfony\web\sf”

<Directory “c:\wamp\bin\php\php5.2.5\PEAR\data\symfony\web\sf”>

AllowOverride All
Allow from All

</Directory>

</VirtualHost>

In lines ‘ Alias /sf “c:\wamp\bin\php\php5.2.5\PEAR\data\symfony\web\sf” ‘ and ‘ <Directory “c:\wamp\bin\php\php5.2.5\PEAR\data\symfony\web\sf”> ‘ replace my path with the path to your symfony/web/sf dir. And do the same with lines ‘ DocumentRoot “c:\wamp\www\your_project\web” ‘ and ‘ <Directory “c:\wamp\www\your_project\web”> ‘ changing the path to one that points to the web directory in your project.

And you should also specify the name of your virtual server by modifying ‘your_application_name’ in the ‘ServerName your_application_name’ line.

Make sure that in the httpd.conf file (main Apache config file located in a directory like C:\wamp\bin\apache\apache2.2.6\conf) the line ‘Include conf/extra/httpd-vhosts.conf‘ is uncommented (no ‘#’ before it).

Now we need to declare our own domain locally, by adding a line like ‘127.0.0.2 your_application_name’ to the host file (located in C:\WINDOWS\system32\drivers\etc). Just make sure that you add your line after ‘127.0.0.1 localhost‘ (which should be in fact the first line). You may also need admin privileges to modify that file.

Now – after an Apache restart – if you type in your browser http://your_application_name/ your Symfony welcoming page should have all the graphics displayed correctly.

Method 2 – project freezing

You can obtain a ready-to-deploy package from your Symfony project by using the freeze command. If you execute in the root of your project:

symfony freeze [c:/path/to/your/symfony/data/dir]

All Symfony core files will be copied to the current project, including the ones that where missing in the web/sf directory. The freeze command also changes some paths in your project configuration so it will now address the Symfony libraries that were also copied to your project not the global ones. The main drawback is that if you want to upgrade Symfony you’ll have to unfreeze (command opposite to freeze) and freeze again all your projects or copy/overwrite files manually. And there may be some path issues if your project is not in the web root of your web server directory.

Method 3 – the stupid way

If the above methods are not working for you – just go ahead and copy the symfony_data_path/web/sf/ directory to your_project_path/web/ (so in my case that would be copying C:\wamp\bin\php\php5.2.5\PEAR\data\symfony\web\sf to the C:\wamp\www\your_project\web directory). As before the downside of this workaround is that after updating Symfony you will have to manually recopy that folder again to all your projects and there probably will be some path issues when accessing plugin assets or when using absolute paths in links (but you probably won’t even notice if you’ll always use symfony helpers for handling your links).