Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Hackday] Update Heroku doc with SYMFONY_ENV param #4545

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 3 commits into from
Closed

[Hackday] Update Heroku doc with SYMFONY_ENV param #4545

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f769b91
[Hackday] Update Heroku doc with SYMFONY_ENV
mxnr Nov 29, 2014
f29279d
[Hackday] Update Heroku doc with SYMFONY_ENV
mxnr Nov 29, 2014
65af592
Update docs with typical Heroku build issue
mxnr Nov 29, 2014
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
Prev Previous commit
Next Next commit
[Hackday] Update Heroku doc with SYMFONY_ENV
  • Loading branch information
@mxnr
mxnr committed Nov 29, 2014
commit f29279d4e4892eb4df2a5a63ccd56a23ecce5db0
4 changes: 2 additions & 2 deletions cookbook/deployment/heroku.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ Configuring Symfony to run in the prod environment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If you don’t explicitly configure the environment (``dev``, ``prod`` etc) to use, Symfony will, by default, use the ``dev`` environment in console commands and at runtime. That would break our build, because in dev environments, Symfony uses the ``SensioGeneratorBundle`` to perform certain tasks, but that bundle is not installed upon a push - `Composer does not install dev packages when pushing to Heroku`_.
For Symfony to know it needs to use the ``prod`` environment at all times, it reads from the ``SYMFONY_ENV`` environment variable. You can simply `set environment variables using the ``heroku config`` feature`_, so run this one command as the last step before deploying your app for the first time:
For Symfony to know it needs to use the ``prod`` environment at all times, it reads from the ``SYMFONY_ENV`` environment variable. You can simply `set environment variables`_ using the ``heroku config`` feature, so run this one command as the last step before deploying your app for the first time:

.. code-block:: bash

Expand Down Expand Up @@ -206,4 +206,4 @@ You should be seeing your Symfony application in your browser.
.. _`Logplex`: https://devcenter.heroku.com/articles/logplex
.. _`verified that the RSA key fingerprint is correct`: https://devcenter.heroku.com/articles/git-repository-ssh-fingerprints
.. _`Composer does not install dev packages when pushing to Heroku`: https://devcenter.heroku.com/articles/php-support#build-behavior
.. _`set environment variables using the ``heroku config`` feature`: https://devcenter.heroku.com/articles/config-vars
.. _`set environment variables`: https://devcenter.heroku.com/articles/config-vars