Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 22cfde2

Browse filesBrowse files
committed
feature #6394 Updated Heroku instructions (magnusnordlander)
This PR was merged into the 2.3 branch. Discussion ---------- Updated Heroku instructions | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | >=2.3 | Fixed tickets | With newer versions of the Heroku toolbelt, multiple buildpacks is supported natively. Commits ------- 204425c Fixed grammatical error 44e44f9 Comment updates 05a0afd Updated Heroku instructions
2 parents 9c4fda7 + 204425c commit 22cfde2
Copy full SHA for 22cfde2

File tree

Expand file treeCollapse file tree

1 file changed

+11
-12
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+11
-12
lines changed

‎cookbook/deployment/heroku.rst

Copy file name to clipboardExpand all lines: cookbook/deployment/heroku.rst
+11-12Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -305,20 +305,20 @@ This is also very useful to build assets on the production system, e.g. with Ass
305305
306306
With the next deploy, Heroku compiles your app using the Node.js buildpack and
307307
your npm packages become installed. On the other hand, your ``composer.json`` is
308-
now ignored. To compile your app with both buildpacks, Node.js *and* PHP, you can
309-
use a special `multiple buildpack`_. To override buildpack auto-detection, you
310-
need to explicitly set the buildpack URL:
308+
now ignored. To compile your app with both buildpacks, Node.js *and* PHP, you need
309+
to use both buildpacks. To override buildpack auto-detection, you
310+
need to explicitly set the buildpack:
311311

312312
.. code-block:: bash
313313
314-
$ heroku buildpacks:set https://github.com/ddollar/heroku-buildpack-multi.git
315-
316-
Next, add a ``.buildpacks`` file to your project, listing the buildpacks you need:
317-
318-
.. code-block:: text
319-
320-
https://github.com/heroku/heroku-buildpack-nodejs.git
321-
https://github.com/heroku/heroku-buildpack-php.git
314+
$ heroku buildpacks:set heroku/nodejs
315+
Buildpack set. Next release on your-application will use heroku/nodejs.
316+
Run git push heroku master to create a new release using this buildpack.
317+
$ heroku buildpacks:set heroku/php --index 2
318+
Buildpack set. Next release on your-application will use:
319+
1. heroku/nodejs
320+
2. heroku/php
321+
Run git push heroku master to create a new release using these buildpacks.
322322
323323
With the next deploy, you can benefit from both buildpacks. This setup also enables
324324
your Heroku environment to make use of node based automatic build tools like
@@ -336,7 +336,6 @@ This is also very useful to build assets on the production system, e.g. with Ass
336336
.. _`custom compile steps`: https://devcenter.heroku.com/articles/php-support#custom-compile-step
337337
.. _`custom Composer command`: https://getcomposer.org/doc/articles/scripts.md#writing-custom-commands
338338
.. _`Heroku buildpacks`: https://devcenter.heroku.com/articles/buildpacks
339-
.. _`multiple buildpack`: https://github.com/ddollar/heroku-buildpack-multi
340339
.. _`Grunt`: http://gruntjs.com
341340
.. _`gulp`: http://gulpjs.com
342341
.. _`Heroku documentation`: https://devcenter.heroku.com/articles/custom-php-settings#nginx

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.