Skip to content

Update deployment.rst #14110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 8, 2021
Merged

Update deployment.rst #14110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions deployment.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Basic File Transfer
The most basic way of deploying an application is copying the files manually
via FTP/SCP (or similar method). This has its disadvantages as you lack control
over the system as the upgrade progresses. This method also requires you
to take some manual steps after transferring the files (see `Common Post-Deployment Tasks`_)
to take some manual steps after transferring the files (see `Common Pre-Post-Deployment Tasks`_)

Using Source Control
~~~~~~~~~~~~~~~~~~~~
Expand All @@ -58,7 +58,7 @@ system. When using Git, a common approach is to create a tag for each release
and check out the appropriate tag on deployment (see `Git Tagging`_).

This makes updating your files *easier*, but you still need to worry about
manually taking other steps (see `Common Post-Deployment Tasks`_).
manually taking other steps (see `Common Pre-Post-Deployment Tasks`_).

Using Platforms as a Service
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down Expand Up @@ -101,10 +101,10 @@ specifically tailored to the requirements of Symfony.
`Symfony plugin`_ is a plugin to ease Symfony related tasks, inspired by `Capifony`_
(which works only with Capistrano 2).

Common Post-Deployment Tasks
----------------------------
Common Pre-Post-Deployment Tasks
--------------------------------

After deploying your actual source code, there are a number of common things
Before and after deploying your actual source code, there are a number of common things
you'll need to do:

A) Check Requirements
Expand Down Expand Up @@ -198,7 +198,7 @@ are simple and more complex tools and one can make the deployment as easy

Don't forget that deploying your application also involves updating any dependency
(typically via Composer), migrating your database, clearing your cache and
other potential things like pushing assets to a CDN (see `Common Post-Deployment Tasks`_).
other potential things like pushing assets to a CDN (see `Common Pre-Post-Deployment Tasks`_).

Troubleshooting
---------------
Expand Down