From 4ee7cef8c405424b08cccc72f3bc7e5ca55268a3 Mon Sep 17 00:00:00 2001 From: Ryan Weaver Date: Sat, 6 Dec 2014 18:47:27 -0500 Subject: [PATCH 1/2] A few more tweaks to outline the steps --- cookbook/deployment/heroku.rst | 33 ++++++++++++++++++++++----------- 1 file changed, 22 insertions(+), 11 deletions(-) diff --git a/cookbook/deployment/heroku.rst b/cookbook/deployment/heroku.rst index 5525e7ffce5..2fead9f5b3d 100644 --- a/cookbook/deployment/heroku.rst +++ b/cookbook/deployment/heroku.rst @@ -69,14 +69,21 @@ You are now ready to deploy the application as explained in the next section. Deploying your Application on Heroku ------------------------------------ -To deploy your application to Heroku, you must first create a ``Procfile``, -which tells Heroku what command to use to launch the web server with the -correct document root. After that, you will ensure that your Symfony application -runs the ``prod`` environment, and then you'll be ready to ``git push`` to -Heroku for your first deploy! +Before your first deploy, you need to do just 2 more things, which are explained +below: -Creating a Procfile -~~~~~~~~~~~~~~~~~~~ +1. :ref:`Create a Procfile ` + +2. :ref:`Set the Environment to prod ` + +Then you'll be ready for the last step: + +3. :ref:`Push your Code to Heroku ` + +.. _heroku-procfile: + +1) Create a Procfile +~~~~~~~~~~~~~~~~~~~~ By default, Heroku will launch an Apache web server together with PHP to serve applications. However, two special circumstances apply to Symfony applications: @@ -111,8 +118,10 @@ create the ``Procfile`` file and to add it to the repository: [master 35075db] Procfile for Apache and PHP 1 file changed, 1 insertion(+) -Setting the ``prod`` Environment -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.. _heroku-setting-env-to-prod: + +2) Set the Environment to prod +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ During a deploy, Heroku runs ``composer install --no-dev`` to install all of the dependencies your application requires. However, typical `post-install-commands`_ @@ -132,8 +141,10 @@ variables, you can issue a single command to prepare your app for a deployment: $ heroku config:set SYMFONY_ENV=prod -Pushing to Heroku -~~~~~~~~~~~~~~~~~ +.. _heroku-push-code: + +3) Push your Code to Heroku +~~~~~~~~~~~~~~~~~~~~~~~~~~~ Next up, it's finally time to deploy your application to Heroku. If you are doing this for the very first time, you may see a message such as the following: From 8c7e3b27cbc2017ec8395d4f091af1aefee98d8f Mon Sep 17 00:00:00 2001 From: Ryan Weaver Date: Sun, 15 Mar 2015 13:19:18 -0400 Subject: [PATCH 2/2] Changing to #. format --- cookbook/deployment/heroku.rst | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/cookbook/deployment/heroku.rst b/cookbook/deployment/heroku.rst index 2fead9f5b3d..6e5c075a577 100644 --- a/cookbook/deployment/heroku.rst +++ b/cookbook/deployment/heroku.rst @@ -72,13 +72,11 @@ Deploying your Application on Heroku Before your first deploy, you need to do just 2 more things, which are explained below: -1. :ref:`Create a Procfile ` +#. :ref:`Create a Procfile ` -2. :ref:`Set the Environment to prod ` +#. :ref:`Set the Environment to prod ` -Then you'll be ready for the last step: - -3. :ref:`Push your Code to Heroku ` +#. :ref:`Push your Code to Heroku ` .. _heroku-procfile: pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy