@@ -63,14 +63,16 @@ manually taking other steps (see `Common Post-Deployment Tasks`_).
63
63
Using Platforms as a Service
64
64
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
65
65
66
- The specific deployment steps vary greatly from one service provider to another,
67
- so check out the dedicated article for the service of your choose :
66
+ Using a Platform as a Service (PAAS) can be a great way to deploy your Symfony app
67
+ quickly and easily. There are many PAAS - below are a few that work well with Symfony :
68
68
69
69
.. toctree ::
70
70
:maxdepth: 1
71
- :glob:
72
71
73
- deployment/*
72
+ deployment/heroku
73
+ deployment/platformsh
74
+ deployment/azure-website
75
+ deployment/fortrabbit
74
76
75
77
Using Build Scripts and other Tools
76
78
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -123,18 +125,16 @@ Check if your server meets the requirements by running:
123
125
124
126
.. _b-configure-your-app-config-parameters-yml-file :
125
127
126
- B) Configure your Parameters File
127
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
128
+ B) Configure your Environment Variables
129
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
128
130
129
- Most Symfony applications define configuration parameters in a file called
130
- ``app/config/parameters.yml ``. This file should *not * be deployed, because
131
- Symfony generates it automatically using the ``app/config/parameters.yml.dist ``
132
- file as a template (that's why ``parameters.yml.dist `` must be committed and
133
- deployed).
131
+ Most Symfony applications read their configuration from environment variables.
132
+ While developing locally, you'll usually store these in a ``.env `` file. But on
133
+ production, instead of creating this file, you should set *real * environment variables.
134
134
135
- If your application uses environment variables instead of these parameters, you
136
- must define those env vars in your production server using the tools provided by
137
- your hosting service.
135
+ How you set environment variables, depends on your setup: they can be set at the
136
+ command line, in your Nginx configuration, or via other methods provided by your
137
+ hosting service.
138
138
139
139
C) Install/Update your Vendors
140
140
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0 commit comments