@@ -94,20 +94,12 @@ with these steps:
9494 $ svn add --force .
9595 $ svn ci -m " add basic Symfony Standard 2.X.Y"
9696
97- #. Copy ``app/config/parameters.yml `` to ``app/config/parameters.yml.dist ``.
98- The ``parameters.yml `` file is ignored by svn (see above) so that
99- machine-specific settings like database passwords aren't committed. By
100- creating the ``parameters.yml.dist `` file, new developers can quickly clone
101- the project, copy this file to ``parameters.yml ``, customize it, and start
102- developing.
103-
104- #. Finally, download all of the third-party vendor libraries by
105- executing Composer. For details, see :ref: `installation-updating-vendors `.
106-
107- .. tip ::
108-
109- If you rely on any "dev" versions, then Git may be used to install
110- those libraries, since there is no archive available for download.
97+ That's it! Since the ``app/config/parameters.yml `` file is ignored, you can
98+ store machine-specific settings like database passwords here without committing
99+ them. The ``parameters.yml.dist `` file *is * committed, but is not read by
100+ Symfony. And by adding any new keys you need to both files, new developers
101+ can quickly clone the project, copy this file to ``parameters.yml ``, customize
102+ it, and start developing.
111103
112104At this point, you have a fully-functional Symfony project stored in your
113105Subversion repository. The development can start with commits in the Subversion
0 commit comments