Skip to content

Changing cookbook/ deployment info #3965

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.

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 21 commits into from
Closed
Changes from 10 commits
Commits
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
23 changes: 18 additions & 5 deletions cookbook/deployment-tools.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,8 @@ There are several ways you can deploy a Symfony2 application.

Start with a few basic deployment strategies and build up from there.



Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove these blank lines.

Basic File Transfer
~~~~~~~~~~~~~~~~~~~

Expand Down Expand Up @@ -71,14 +73,24 @@ Common Post-Deployment Tasks
After deploying your actual source code, there are a number of common things
you'll need to do:

A) Configure your ``app/config/parameters.yml`` file
A) Check requirements.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requirements

and there is no need for the full stop

~~~~~~~~~~~~~~~~~~~~~~

Check if your server meets requirements.
Run command:

.. code-block:: bash

$ php app/check.php

B) Configure your ``app/config/parameters.yml`` file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

File

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This file should be customized on each system. The method you use to
deploy your source code should *not* deploy this file. Instead, you should
set it up manually (or via some build process) on your server(s).

B) Update your vendors
C) Update your vendors
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vendors

~~~~~~~~~~~~~~~~~~~~~~

Your vendors can be updated before transferring your source code (i.e.
Expand All @@ -97,7 +109,7 @@ as you normally do:
ensures that development packages are not installed in the production
environment.

C) Clear your Symfony cache
D) Clear your Symfony cache
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cache

~~~~~~~~~~~~~~~~~~~~~~~~~~~

Make sure you clear (and warm-up) your Symfony cache:
Expand All @@ -106,7 +118,7 @@ Make sure you clear (and warm-up) your Symfony cache:

$ php app/console cache:clear --env=prod --no-debug

D) Dump your Assetic assets
E) Dump your Assetic assets
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assets

~~~~~~~~~~~~~~~~~~~~~~~~~~~

If you're using Assetic, you'll also want to dump your assets:
Expand All @@ -115,7 +127,7 @@ If you're using Assetic, you'll also want to dump your assets:

$ php app/console assetic:dump --env=prod --no-debug

E) Other things!
F) Other things!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Things

~~~~~~~~~~~~~~~~

There may be lots of other things that you need to do, depending on your
Expand All @@ -126,6 +138,7 @@ setup:
* Running ``assets:install`` (taken care of already in ``composer.phar install``)
* Add/edit CRON jobs
* Pushing assets to a CDN
* Change default Favicon (web/favicon.ico)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not related to deploying.

* ...

Application Lifecycle: Continuous Integration, QA, etc
Expand Down