Skip to content

Commit 7d03251

Browse files
committed
minor #14690 [Set-up] Change order of first sections (wouterj)
This PR was merged into the 4.4 branch. Discussion ---------- [Set-up] Change order of first sections Fixes #14680 | *Before* | *After* | | --- | --- | | Creating Symfony Applications<br>Running Symfony Applications<br>Setting up an Existing Symfony Project | Creating Symfony Applications<br>Setting up an Existing Symfony Project<br>Running Symfony Applications | Commits ------- 81a0208 Change order in Set-up article
2 parents 81d633b + 81a0208 commit 7d03251

File tree

1 file changed

+29
-29
lines changed

1 file changed

+29
-29
lines changed

setup.rst

+29-29
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,35 @@ started. In other words, your new application is ready!
8181
and ``<project>/var/log/``) must be writable by the web server. If you have
8282
any issue, read how to :doc:`set up permissions for Symfony applications </setup/file_permissions>`.
8383

84+
.. _install-existing-app:
85+
86+
Setting up an Existing Symfony Project
87+
--------------------------------------
88+
89+
In addition to creating new Symfony projects, you will also work on projects
90+
already created by other developers. In that case, you only need to get the
91+
project code and install the dependencies with Composer. Assuming your team uses
92+
Git, setup your project with the following commands:
93+
94+
.. code-block:: terminal
95+
96+
# clone the project to download its contents
97+
$ cd projects/
98+
$ git clone ...
99+
100+
# make Composer install the project's dependencies into vendor/
101+
$ cd my-project/
102+
$ composer install
103+
104+
You'll probably also need to customize your :ref:`.env file <config-dot-env>`
105+
and do a few other project-specific tasks (e.g. creating a database). When
106+
working on a existing Symfony application for the first time, it may be useful
107+
to run this command which displays information about the project:
108+
109+
.. code-block:: terminal
110+
111+
$ php bin/console about
112+
84113
Running Symfony Applications
85114
----------------------------
86115

@@ -112,35 +141,6 @@ the server by pressing ``Ctrl+C`` from your terminal.
112141
The web server works with any PHP application, not only Symfony projects,
113142
so it's a very useful generic development tool.
114143

115-
.. _install-existing-app:
116-
117-
Setting up an Existing Symfony Project
118-
--------------------------------------
119-
120-
In addition to creating new Symfony projects, you will also work on projects
121-
already created by other developers. In that case, you only need to get the
122-
project code and install the dependencies with Composer. Assuming your team uses
123-
Git, setup your project with the following commands:
124-
125-
.. code-block:: terminal
126-
127-
# clone the project to download its contents
128-
$ cd projects/
129-
$ git clone ...
130-
131-
# make Composer install the project's dependencies into vendor/
132-
$ cd my-project/
133-
$ composer install
134-
135-
You'll probably also need to customize your :ref:`.env file <config-dot-env>`
136-
and do a few other project-specific tasks (e.g. creating a database). When
137-
working on a existing Symfony application for the first time, it may be useful
138-
to run this command which displays information about the project:
139-
140-
.. code-block:: terminal
141-
142-
$ php bin/console about
143-
144144
.. _symfony-flex:
145145

146146
Installing Packages

0 commit comments

Comments
 (0)