Skip to content

Commit f610a8a

Browse files
authored
Update Heroku instructions
* Use `heroku buildpacks:add` instead of `:set` so existing buildpacks aren't overwritten * Replace deprecated ABASystems' apt buildpack (redirects to uptick/heroku-buildpack-apt, which hasn't been updated in 3 years, forked from ddollar/heroku-buildpack-apt, which explicitly says it's deprecated) with Heroku's (https://github.com/heroku/heroku-buildpack-apt) * Replace ABASystems' python buildpack with Heroku's (heroku/python)
1 parent 619ae0a commit f610a8a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1249,8 +1249,8 @@ Getting ``python3-saml`` up and running on Heroku will require some extra legwor
12491249
First you will need to add the ```apt``` buildpack to your build server:
12501250

12511251
```
1252-
heroku buildpacks:set --index=1 -a your-app https://github.com/ABASystems/heroku-buildpack-apt
1253-
heroku buildpacks:set --index=2 -a your-app https://github.com/ABASystems/heroku-buildpack-python
1252+
heroku buildpacks:add --index=1 -a your-app heroku-community/apt
1253+
heroku buildpacks:add --index=2 -a your-app heroku/python
12541254
```
12551255

12561256
You can confirm the buildpacks have been added in the correct order with ```heroku buildpacks -a your-app```, you should see the apt buildpack first followed by the Python buildpack.

0 commit comments

Comments
 (0)