|
4 | 4 | Installing and Configuring Symfony |
5 | 5 | ================================== |
6 | 6 |
|
7 | | -The goal of this chapter is to get you up-and-running with a working application |
| 7 | +The goal of this chapter is to get you up and running with a working application |
8 | 8 | built on top of Symfony. Fortunately, Symfony offers "distributions", which |
9 | 9 | are functional Symfony "starter" projects that you can download and begin |
10 | 10 | developing in immediately. |
@@ -35,7 +35,7 @@ Symfony2 distribution. Here, you'll need to make two choices: |
35 | 35 | on your computer, you should download Symfony2 "without vendors", as it |
36 | 36 | adds a bit more flexibility when including third-party/vendor libraries. |
37 | 37 |
|
38 | | -Download one of the archives somewhere under your local web server/s root |
| 38 | +Download one of the archives somewhere under your local web server's root |
39 | 39 | directory and unpack it. From a UNIX command line, this can be done with |
40 | 40 | one of the following commands (replacing ``###`` with your actual filename): |
41 | 41 |
|
@@ -94,7 +94,7 @@ sample code inside the ``src/`` directory. |
94 | 94 |
|
95 | 95 | Symfony2 comes with a visual server configuration tester to help make sure |
96 | 96 | your Web server and PHP are configured to use Symfony. Use the following URL |
97 | | -URL to check your configuration: |
| 97 | +to check your configuration: |
98 | 98 |
|
99 | 99 | .. code-block:: text |
100 | 100 |
|
@@ -142,23 +142,41 @@ development! Your distribution may contain some sample code - check the |
142 | 142 | to learn about what sample code was included with your distribution and how |
143 | 143 | you can remove it later. |
144 | 144 |
|
| 145 | +If you're new to Symfony, join us in the ":doc:`page_creation`", where you'll |
| 146 | +learn how to create pages, change configuration, and do everything else you'll |
| 147 | +need in your new application. |
| 148 | + |
145 | 149 | Using Source Control |
146 | | -~~~~~~~~~~~~~~~~~~~~ |
| 150 | +-------------------- |
147 | 151 |
|
148 | 152 | If you're using a version control system like ``Git`` or ``Subversion``, you |
149 | | -can begin committing your project as normal. If you've downloaded the archive |
150 | | -*without vendors*, you can safely ignore the entire ``vendors/`` directory |
151 | | -and not commit it to source control. With ``Git``, this is done by creating |
152 | | -and adding the following to a ``.gitignore`` file: |
| 153 | +can setup your version control system and begin committing your project to |
| 154 | +it as normal. For ``Git``, this can be done easily with the following command: |
| 155 | + |
| 156 | +.. code-block:: bash |
| 157 | +
|
| 158 | + git init |
| 159 | +
|
| 160 | +For more information on setting up and using Git, check out the `GitHub Bootcamp`_ |
| 161 | +tutorials. |
| 162 | + |
| 163 | +Ignoring the ``vendor/`` Directory |
| 164 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 165 | + |
| 166 | +If you've downloaded the archive *without vendors*, you can safely ignore |
| 167 | +the entire ``vendors/`` directory and not commit it to source control. With |
| 168 | +``Git``, this is done by creating and adding the following to a ``.gitignore`` |
| 169 | +file: |
153 | 170 |
|
154 | 171 | .. code-block:: text |
155 | 172 |
|
156 | 173 | vendor/ |
157 | 174 |
|
158 | 175 | Now, the vendor directory won't be committed to source control. This is fine |
159 | | -(actually, it's great!) because when someone else clones our checks out the |
| 176 | +(actually, it's great!) because when someone else clones or checks out the |
160 | 177 | project, he/she can simply run the ``php bin/vendors.php`` script to download |
161 | 178 | all the necessary vendor libraries. |
162 | 179 |
|
163 | 180 | .. _`http://symfony.com/download`: http://symfony.com/download |
164 | | -.. _`Git`: http://git-scm.com/ |
| 181 | +.. _`Git`: http://git-scm.com/ |
| 182 | +.. _`GitHub Bootcamp`: http://help.github.com/set-up-git-redirect |
0 commit comments