The document provides instructions for installing and setting up the Symfony PHP framework. It discusses different installation methods like using the sandbox, PEAR, or SVN. It also covers generating a new Symfony project and application, configuring the web server, and troubleshooting common issues. Version control of Symfony projects using Subversion is also described.

1. Wildan Maulana | wildan [at] tobethink.com #3 The Definitive Guide to symfony Running Symfony Doc. v. 0.1 - 14/04/09

4. Use PEAR installation method, it is recommended for most people

5. Use Subversion (SVN) installation, it is meant to be used by advanced PHP developers, who want to take advantage of the latest patches, add features of their own, and/or contribute to the symfony project. Btw, I prefer using SVN installation method

10. Using Subversion (SVN)

12. To see the libraries available in this channel, type the following: > pear remote-list -c symfony

13. Now you are ready to install the latest stable version of symfony. Issue this command: > pear install symfony/symfony

14. downloading symfony-1.2.0.tgz ...

15. Starting to download symfony-1.2.0.tgz (1,283,270 bytes)

16. .................................................................

17. .................................................................

18. .............done: 1,283,270 bytes

19. install ok: channel://pear.symfony-project.com/symfony-1.2.0

20. Check that the installation succeeded > symfony -V

21. symfony version 1.2.0 (/path/to/the/pear/symfony/lib/dir)

23. $data_dir/symfony / contains the web assets used by symfony default modules.

24. $doc_dir/symfony/ contains the documentation.

27. # > cd /path/to/symfony

28. # > svn checkout http://svn.symfony-project.com/tags/RELEASE_1_2_0/

29. > php /path/to/symfony/data/bin/symfony -V

30. symfony version 1.2.0 (/path/to/the/svn/symfony/lib/dir) <?php require_once '/path/to/symfony/lib/autoload/sfCoreAutoload.class.php'; sfCoreAutoload::register(); class ProjectConfiguration extends sfProjectConfiguration { // ... }

32. Creating the Application

33. Creating Project For a PEAR installation, issue these commands: > mkdir ~/myproject > cd ~/myproject > symfony generate:project myproject For an SVN installation, create a project with these commands: > mkdir ~/myproject > cd ~/myproject > php /path/to/symfony/data/bin/symfony generate:project myproject apps/ cache/ config/ data/ doc/ lib/ log/ plugins/ test/ web/ Symfony will create a directory structure that looks like this:

35. To initialize application use the symfony generate:app command >php symfony generate:app frontend

36. This will create a frontend/ directory in the apps/ folder of the project root, with a default application configuration and a set of directories ready to host the file of your website: apps/ frontend/ config/ i18n/ lib/ modules/ templates/ web/ index.php frontend_dev.php index.php -> front controller in production environment frontend_dev.php -> front controller in development environment

38. Setting Up an Alias

39. Configuring a Shared-Host Server

40. Setting Up a Virtual Host <VirtualHost *:80> ServerName myapp.example.com DocumentRoot &quot;/home/steve/myproject/web&quot; DirectoryIndex index.php Alias /sf /$sf_symfony_data_dir/web/sf <Directory &quot;/$sf_symfony_data_dir/web/sf&quot;> AllowOverride All Allow from All </Directory> <Directory &quot;/home/steve/myproject/web&quot;> AllowOverride All Allow from All </Directory> </VirtualHost> Don't fortget to setup your DNS entry for your application address first

41. Setting Up an Alias

43. .htaccess Options +FollowSymLinks +ExecCGI <IfModule mod_rewrite.c> RewriteEngine On # uncomment the following line, if you are having trouble # getting no_script_name to work #RewriteBase / # we skip all files with .something #RewriteCond %{REQUEST_URI} .+$ #RewriteCond %{REQUEST_URI} !html$ #RewriteRule .* - [L] # we check if the .html version is here (caching) RewriteRule ^$ index.html [QSA] RewriteRule ^([^.]+)$ $1.html [QSA] RewriteCond %{REQUEST_FILENAME} !-f # no, so we redirect to our front web controller RewriteRule ^(.*)$ index.php [QSA,L] </IfModule>

44. Browse Your New App http://www.example.com/frontend_dev.php/

46. Allowed memory size of 8388608 bytes exhausted

47. Strict Standards: Implicit cloning object of class 'sfTimer'because of 'zend.ze1_compatibility_mode'

48. sfCacheException [message] Unable to write cache file&quot;/usr/myproject/cache/frontend/prod/config/config_config_handlers.yml.php&quot;

49. The include path of your system must include the path to the php command, and the include path of your php.ini must contain a path to PEAR (if you use PEAR).

50. Sometimes, there is more than one php.ini on a server's file system (for instance, if you use the WAMP package). Call phpinfo() to know the exact location of the php.ini file used by your application.

52. The archives of the users mailing-list (http://groups.google.fr/group/symfony-users)

53. The symfony wiki (http://trac.symfony-project.org/

55. > svn mkdir -m &quot;layout creation&quot; file:///$SVNREP_DIR/myproject/trunk file:///$SVNREP_DIR/myproject/tags file:///$SVNREP_DIR/myproject/branches

56. > cd ~/myproject

57. rm -rf cache/*

58. rm -rf log/*

59. svn import -m &quot;initial import&quot; . file:///$SVNREP_DIR/myproject/trunk

60. > svn ls file:///$SVNREP_DIR/myproject/trunk/

61. > cd ~

62. > mv myproject myproject.origin

63. > svn co file:///$SVNREP_DIR/myproject/trunk myproject

64. > ls myproject

65. > cd ~/myproject

66. > chmod 777 cache

67. > chmod 777 log

68. > svn propedit svn:ignore log

69. > svn propedit svn:ignore cache

70. > export SVN_EDITOR=<name of editor>

71. > svn propedit svn:ignore log

72. > svn propedit svn:ignore cache

73. Write * , save and quit.

74. You're finished

76. For real development, consider to use the SVN version

77. Once your project is initiated, it is a good habit to start a version-control process.

78. Q&A