@@ -14,23 +14,26 @@ developing in immediately.
14
14
If you're looking for instructions on how best to create a new project
15
15
and store it via source control, see `Using Source Control `_.
16
16
17
- Downloading a Symfony2 Distribution
18
- -----------------------------------
17
+ Installing a Symfony2 Distribution
18
+ ----------------------------------
19
19
20
20
.. tip ::
21
21
22
- First, check that you have installed and configured a Web server (such
23
- as Apache) with PHP 5.3.3 or higher. For more information on Symfony2
24
- requirements, see the :doc: `requirements reference</reference/requirements> `.
25
- For information on configuring your specific web server document root, see the
26
- following documentation: `Apache `_ | `Nginx `_ .
22
+ First, check that you have installed and configured a Web server (such as
23
+ Apache) with the most recent PHP version possible (PHP 5.3.8 or newer is
24
+ recommended). For more information on Symfony2 requirements, see the
25
+ :doc: `requirements reference</reference/requirements> `. For information on
26
+ configuring your specific web server document root, see the following
27
+ documentation: `Apache `_ | `Nginx `_ .
27
28
28
29
Symfony2 packages "distributions", which are fully-functional applications
29
30
that include the Symfony2 core libraries, a selection of useful bundles, a
30
31
sensible directory structure and some default configuration. When you download
31
32
a Symfony2 distribution, you're downloading a functional application skeleton
32
33
that can be used immediately to begin developing your application.
33
34
35
+
36
+
34
37
Start by visiting the Symfony2 download page at `http://symfony.com/download `_.
35
38
On this page, you'll see the *Symfony Standard Edition *, which is the main
36
39
Symfony2 distribution. Here, you'll need to make two choices:
@@ -99,34 +102,33 @@ Symfony itself - into the ``vendor/`` directory.
99
102
100
103
.. note ::
101
104
102
- If you don't have ``curl `` installed, you can also just download the ``installer ``
103
- file manually at http://getcomposer.org/installer. Place this file into your
104
- project and then run:
105
+ If you don't have ``curl `` installed, you can also just download the ``installer ``
106
+ file manually at http://getcomposer.org/installer. Place this file into your
107
+ project and then run:
108
+
109
+ .. code-block :: bash
105
110
106
- .. code-block :: bash
111
+ php installer
112
+ php composer.phar install
107
113
108
- php installer
109
- php composer.phar install
110
-
111
114
.. tip ::
112
115
113
- When running ``php composer.phar install `` or ``php composer.phar update ``, composer will execute
114
- post install/update commands to clear the cache and install assets. By default, the assets will be
115
- copied into your ``web `` directory. To create symlinks instead of copying the assets, you
116
- can add an entry in the ``extra `` node of your composer.json file with the key ``symfony-assets-install ``
117
- and the value ``symlink ``:
118
-
119
- .. code-block :: json
120
-
121
- "extra" : {
122
- "symfony-app-dir" : " app" ,
123
- "symfony-web-dir" : " web" ,
124
- "symfony-assets-install" : " symlink"
125
- }
126
-
127
- When passing ``relative `` instead of ``symlink `` to symfony-assets-install, the command will generate
128
- relative symlinks.
129
-
116
+ When running ``php composer.phar install `` or ``php composer.phar update ``, composer will execute
117
+ post install/update commands to clear the cache and install assets. By default, the assets will be
118
+ copied into your ``web `` directory. To create symlinks instead of copying the assets, you
119
+ can add an entry in the ``extra `` node of your composer.json file with the key ``symfony-assets-install ``
120
+ and the value ``symlink ``:
121
+
122
+ .. code-block :: json
123
+
124
+ "extra" : {
125
+ "symfony-app-dir" : " app" ,
126
+ "symfony-web-dir" : " web" ,
127
+ "symfony-assets-install" : " symlink"
128
+ }
129
+
130
+ When passing ``relative `` instead of ``symlink `` to symfony-assets-install, the command will generate
131
+ relative symlinks.
130
132
131
133
Configuration and Setup
132
134
~~~~~~~~~~~~~~~~~~~~~~~
@@ -169,9 +171,9 @@ If there are any issues, correct them now before moving on.
169
171
170
172
**2. Using Acl on a system that does not support chmod +a **
171
173
172
- Some systems don't support ``chmod +a ``, but do support another utility
174
+ Some systems don't support ``chmod +a ``, but do support another utility
173
175
called ``setfacl ``. You may need to `enable ACL support `_ on your partition
174
- and install setfacl before using it (as is the case with Ubuntu), like
176
+ and install setfacl before using it (as is the case with Ubuntu), like
175
177
so:
176
178
177
179
.. code-block :: bash
@@ -249,12 +251,12 @@ file:
249
251
250
252
.. code-block :: text
251
253
252
- vendor/
254
+ / vendor/
253
255
254
256
Now, the vendor directory won't be committed to source control. This is fine
255
257
(actually, it's great!) because when someone else clones or checks out the
256
258
project, he/she can simply run the ``php composer.phar install `` script to
257
- download all the necessary vendor libraries .
259
+ install all the necessary project dependencies .
258
260
259
261
.. _`enable ACL support` : https://help.ubuntu.com/community/FilePermissionsACLs
260
262
.. _`http://symfony.com/download` : http://symfony.com/download
0 commit comments