You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* 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)
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1249,8 +1249,8 @@ Getting ``python3-saml`` up and running on Heroku will require some extra legwor
1249
1249
First you will need to add the ```apt``` buildpack to your build server:
1250
1250
1251
1251
```
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
1254
1254
```
1255
1255
1256
1256
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