From bc5ad90f54c62fb03b98baac561b61f4eb11c760 Mon Sep 17 00:00:00 2001 From: Ryan Weaver Date: Wed, 24 Oct 2018 09:36:49 -0400 Subject: [PATCH] Clarifying that .env can be used on production --- deployment.rst | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-) diff --git a/deployment.rst b/deployment.rst index 365c0837bdf..f5446eed0b4 100644 --- a/deployment.rst +++ b/deployment.rst @@ -125,16 +125,27 @@ B) Configure your Environment Variables ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Most Symfony applications read their configuration from environment variables. -While developing locally, you'll usually store these in a ``.env`` file. But on -production, instead of creating this file, you should set *real* environment variables. +While developing locally, you'll usually store these in a ``.env`` file. On production, +you have two options: -How you set environment variables, depends on your setup: they can be set at the -command line, in your Nginx configuration, or via other methods provided by your -hosting service. +1. Create "real" environment variables. How you set environment variables, depends + on your setup: they can be set at the command line, in your Nginx configuration, + or via other methods provided by your hosting service. -At the very least you need to define the ``APP_ENV=prod`` environment variable -to run the application in ``prod`` mode, but depending on your application you -may need to define other env vars too. +2. Or, create a ``.env`` file just like your local development (see note below) + +There is no significant advantage to either of the two options: use whatever is +most natural in your hosting environment. + +.. note:: + + If you use the ``.env`` file on production, you may need to move your + ``symfony/dotenv`` dependency from ``require-dev`` to ``require`` in ``composer.json``: + + .. code-block:: terminal + + $ composer remove symfony/dotenv + $ composer reuire symfony/dotenv C) Install/Update your Vendors ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~