Commit 3e564ef1 authored by Max Lynch's avatar Max Lynch

fix(README): heroku buildpack:set not config:set

config:set wasn't enough to change the buildpack if you already had one set. Changed it to heroku buildpack:set to match the docs here: https://devcenter.heroku.com/articles/buildpacks
parent 40214da8
......@@ -37,7 +37,7 @@ For most Node.js apps this buildpack should work just fine.
If, however, you're unable to deploy using this new version of the buildpack, you can get your app working again by locking it to the previous version:
```
heroku config:set BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-nodejs#v63 -a my-app
heroku buildpack:set BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-nodejs#v63 -a my-app
git commit -am "empty" --allow-empty
git push heroku master
```
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment