Skip to content
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.

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

Added a new "Deploying to Heroku Cloud" cookbook article #4045

Closed
wants to merge 8 commits into from
Closed

Added a new "Deploying to Heroku Cloud" cookbook article #4045

wants to merge 8 commits into from

Conversation

javiereguiluz
Copy link
Member

Q A
Doc fix? no
New docs? yes
Applies to master
Fixed tickets -

@wouterj
Copy link
Member

wouterj commented Jul 23, 2014

It should also be added to cookbook/map.rst.inc

=========================

This step by step cookbook describes how to deploy a Symfony2 web application to
the Heroku cloud platform. Its contents are based on `this original article`_
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say "the original article"

@javiereguiluz
Copy link
Member Author

@wouterj thanks for your exhaustive review. Awesome work as always!

Regarding the contents of this tutorial, I'd like to add two things:

  • The technical part of this article should be correct because it has been written by Heroku and validated by independent companies, such as SensioLabs.
  • Most of the contents have been borrowed from the original tutorial published by Heroku but we've been legally entitled to do so.

@javiereguiluz javiereguiluz changed the title First draft of "Deploying to Heroku Cloud" cookbook article Added a new "Deploying to Heroku Cloud" cookbook article Jul 24, 2014
~~~~~~~~~~~~~~~~~~~~~~~~~~

Deploying a Symfony2 application to Heroku doesn't require any change in its
code, but it requires some minor tweaks in its configuration.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"[...] tweaks to its configuration"?

@javiereguiluz
Copy link
Member Author

@xabbuh thanks for your great review! I've applied each and every suggestion.

@xabbuh
Copy link
Member

xabbuh commented Jul 25, 2014

@javiereguiluz Thanks for this great article. I'll try to review the rest of it later today.

Deploying your Application on Heroku
------------------------------------

To deploy your application to Heroku, you must first create a ``Procfile``,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this really called "Procfile" and not "Profile"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@xabbuh I know that Procfile sounds awful, but I've checked it again and it's definitely the correct name in this context :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@javiereguiluz Thanks for clarifying. :)

Vendor binaries are usually installed to ``vendor/bin`` by Composer, but
sometimes (e.g. when running a Symfony Standard Edition project!), the
location will be different. If in doubt, you can always run
``composer config bin-dir`` to figure out the right location.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this note misleading since you already wrote in the list before that the bin dir is bin/?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I should probably reword the text to simplify it. Any suggestions to do it? Thanks!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm ok with this, but we can open a new PR if some better wording comes to us. I kind of like the discussion about how the SE differs from the default.

@weaverryan
Copy link
Member

Great job Javier! I loved reading through this! I only had one comment.

@weaverryan
Copy link
Member

Merged! This is so great - thanks Javier! I'd like to see more of these things, especially if we can partner we're avoiding duplication (e.g. if Heroku knows they can suggest any changes/improvements here and link to these docs instead of creating their own). And if there are docs elsewhere (e.g. Capifony), we could still have these, but link out to those docs (and help improve them). Anyways, thanks!

@wouterj
Copy link
Member

wouterj commented Jul 30, 2014

@javiereguiluz I really appreciate that you want to give credits to the reviewers, but could you please remove the mention (the @ character) from the commit message the next time? Now, I get 5 notifications because of the mention (one of the commit itself when the PR is merged, one of the merge commit, and 3 merge commits 2.3 -> 2.4, 2.4 -> 2.5, 2.5 -> master). Thank you and keep up the good work!

@javiereguiluz
Copy link
Member Author

I'm really sorry Wouter. Excuse me for the noise :(

I'll try really hard to not doing it again. However, I'm so used to it, that I could mistakenly do it again in the future. I apologize in advance :)

@wouterj
Copy link
Member

wouterj commented Jul 30, 2014

@javiereguiluz don't worry too much :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants