Skip to content

Commit 41f415a

Browse files
committed
minor #7319 Update deployment.rst (jepster, javiereguiluz)
This PR was submitted for the 2.8 branch but it was merged into the 2.7 branch instead (closes #7319). Discussion ---------- Update deployment.rst Commits ------- 324641b Minor reword 01291bc Update deployment.rst
2 parents 7fa7110 + 324641b commit 41f415a

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

deployment.rst

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,10 @@ Using Source Control
5252
~~~~~~~~~~~~~~~~~~~~
5353

5454
If you're using source control (e.g. Git or SVN), you can simplify by having
55-
your live installation also be a copy of your repository. When you're ready
56-
to upgrade it is as simple as fetching the latest updates from your source
57-
control system.
55+
your live installation also be a copy of your repository. When you're ready to
56+
upgrade it is as simple as fetching the latest updates from your source control
57+
system. When using Git, a common approach is to create a tag for each release
58+
and check out the appropriate tag on deployment (see `Git Tagging`_).
5859

5960
This makes updating your files *easier*, but you still need to worry about
6061
manually taking other steps (see `Common Post-Deployment Tasks`_).
@@ -206,6 +207,7 @@ Don't forget that deploying your application also involves updating any dependen
206207
(typically via Composer), migrating your database, clearing your cache and
207208
other potential things like pushing assets to a CDN (see `Common Post-Deployment Tasks`_).
208209

210+
.. _`Git Tagging`: https://git-scm.com/book/en/v2/Git-Basics-Tagging
209211
.. _`Capifony`: https://github.com/everzet/capifony
210212
.. _`Capistrano`: http://capistranorb.com/
211213
.. _`sf2debpkg`: https://github.com/liip/sf2debpkg

0 commit comments

Comments
 (0)