Skip to content

Commit 2fdfd6d

Browse files
committed
Fixed all problems reported by @wouterj
1 parent 31003b2 commit 2fdfd6d

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

cookbook/deployment/heroku.rst

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,20 +5,20 @@ Deploying to Heroku Cloud
55
=========================
66

77
This step by step cookbook describes how to deploy a Symfony2 web application to
8-
the Heroku cloud platform. Its contents are based on `this original article`_
8+
the Heroku cloud platform. Its contents are based on `the original article`_
99
published by Heroku.
1010

1111
Setting up
1212
----------
1313

1414
To setup a new Heroku website, first `signup with Heroku`_ or sign in
15-
with your credentials. Then, download and install the `Heroku Toolbet`_ on your
15+
with your credentials. Then download and install the `Heroku Toolbet`_ on your
1616
local computer.
1717

1818
You can also check out the `getting Started with PHP on Heroku`_ guide to gain
1919
more familiarity with the specifics of working with PHP applications on Heroku.
2020

21-
Preparing your application
21+
Preparing your Application
2222
~~~~~~~~~~~~~~~~~~~~~~~~~~
2323

2424
Deploying a Symfony2 application to Heroku doesn't require any change in its
@@ -28,7 +28,7 @@ By default, the Symfony2 app will log into your application's ``app/log/``
2828
directory, which isn't ideal as Heroku uses an `ephemeral file system`_. On
2929
Heroku, the best way to handle logging is using Logplex, and the best way to
3030
send log data to Logplex is by writing to ``STDERR`` or ``STDOUT``. Luckily
31-
Symfony2 uses the excellent Monolog library for logging, and so a new log
31+
Symfony2 uses the excellent Monolog library for logging and so a new log
3232
destination is just a config file change away.
3333

3434
Open ``app/config/config_prod.yml`` file, locate ``monolog/handlers/nested``
@@ -44,13 +44,12 @@ section and change the value of ``path`` from
4444
# ...
4545
nested:
4646
# ...
47-
# path: %kernel.logs_dir%/%kernel.environment%.log
4847
path: "php://stderr"
4948
5049
Once the application is deployed, run ``heroku logs --tail`` to keep the
5150
stream of logs from Heroku open in your terminal.
5251

53-
Creating a new application on Heroku
52+
Creating a New Application on Heroku
5453
------------------------------------
5554

5655
To create a new Heroku application that you can push to, use the CLI ``create``
@@ -66,12 +65,12 @@ command:
6665
6766
You are now ready to deploy the application as explained in the next section.
6867

69-
Deploying your application on Heroku
68+
Deploying your Application on Heroku
7069
------------------------------------
7170

7271
To deploy your application to Heroku, you must first create a ``Procfile``,
7372
which tells Heroku what command to use to launch the web server with the
74-
correct settings. After you've done that, you can simply ``git push``, and
73+
correct settings. After you've done that, you can simply ``git push`` and
7574
you're done!
7675

7776
Creating a Procfile
@@ -175,15 +174,16 @@ Then, deploy your application executing this command:
175174
To git@heroku.com:mighty-hamlet-1981.git
176175
* [new branch] master -> master
177176
178-
**And that's it!** If you now open your browser, either by manually pointing
179-
it to the URL ``heroku create`` gave you, or by using the Heroku Toolbelt, the application will respond:
177+
And that's it! If you now open your browser, either by manually pointing
178+
it to the URL ``heroku create`` gave you, or by using the Heroku Toolbelt, the
179+
application will respond:
180180

181181
.. code-block:: bash
182182
183183
$ heroku open
184184
Opening mighty-hamlet-1981... done
185185
186-
*Et voilà!* You should be seeing your Symfony2 application in your browser.
186+
You should be seeing your Symfony2 application in your browser.
187187

188188
.. _`this original article`: https://devcenter.heroku.com/articles/getting-started-with-symfony2
189189
.. _`signup with Heroku`: https://signup.heroku.com/signup/dc

0 commit comments

Comments
 (0)