Skip to content

Commit 3c16e22

Browse files
committed
Merge pull request #12 from aidanlister/patch-1
Add information about getting the demos up and running on Heroku
2 parents fb18c40 + 74d5dfb commit 3c16e22

1 file changed

Lines changed: 21 additions & 0 deletions

File tree

README.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1035,3 +1035,24 @@ Once the SP is configured, the metadata of the SP is published at the /metadata
10351035
####How it works####
10361036

10371037
This demo works very similar to the flask-demo (We did it intentionally).
1038+
1039+
###Getting up and running on Heroku###
1040+
1041+
Getting python3-saml up and running on Heroku will require some extra legwork: python3-saml depends on python-xmlsec which depends on headers from the xmlsec1-dev linux package to install correctly.
1042+
1043+
First you will need to add the ```apt``` buildpack to your build server:
1044+
1045+
```
1046+
heroku buildpacks:set --index=1 -a your-app https://github.com/ABASystems/heroku-buildpack-apt
1047+
heroku buildpacks:set --index=2 -a your-app https://github.com/ABASystems/heroku-buildpack-python
1048+
```
1049+
1050+
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.
1051+
1052+
Then add an ```Aptfile``` into the root of your repository containing the ```libxmlsec1-dev``` package, the file should look like:
1053+
```
1054+
libxmlsec1-dev
1055+
1056+
```
1057+
1058+
Finally, add python3-saml to your requrements.txt and ```git push``` to trigger a build.

0 commit comments

Comments
 (0)