Skip to content

Update deployment.rst #7813

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

Closed
wants to merge 2 commits into from
Closed

Update deployment.rst #7813

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bbb22f2
Update deployment.rst
timothymctim Apr 17, 2017
b0f141b
Minor reword
javiereguiluz Apr 18, 2017
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
10 changes: 5 additions & 5 deletions deployment.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ specifically tailored to the requirements of Symfony.
`Capistrano`_ with `Symfony plugin`_
`Capistrano`_ is a remote server automation and deployment tool written in Ruby.
`Symfony plugin`_ is a plugin to ease Symfony related tasks, inspired by `Capifony`_
(which works only with Capistrano 2 )
(which works only with Capistrano 2).

`sf2debpkg`_
Helps you build a native Debian package for your Symfony project.
Expand Down Expand Up @@ -181,12 +181,12 @@ setup:
* Pushing assets to a CDN
* ...

Application Lifecycle: Continuous Integration, QA, etc
------------------------------------------------------
Application Lifecycle: Continuous Integration, QA, etc.
-------------------------------------------------------

While this entry covers the technical details of deploying, the full lifecycle
of taking code from development up to production may have a lot more steps
(think deploying to staging, QA (Quality Assurance), running tests, etc).
of taking code from development up to production may have more steps:
deploying to staging, QA (Quality Assurance), running tests, etc.

The use of staging, testing, QA, continuous integration, database migrations
and the capability to roll back in case of failure are all strongly advised. There
Expand Down