-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(staticman): use wd15-staticman.herokuapp.com #1025
Conversation
Use wd15-staticman.herokuapp.com instead of https://dev.staticman.net to test new PFHub Staticman instance hosted on Heroku.
"More stable" in that we expect Heroku to have better uptime than Staticman? |
@wd15, please comment on the impact of this change on maintainability of PFHub. |
Few reasons for this change (nothing to do with uptime or Heroku as the public instance is also hosted from Heroku):
Some relevant comments:
|
It'll make it easier to maintain if anything as we won't have to deal with Staticman end points changing and having no control over the app. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Address #899
Use wd15-staticman.herokuapp.com instead of https://dev.staticman.net
for new PFHub Staticman instance hosted on Heroku.
Running up against "Application Error' when using https://dev.staticman.net, which is the public instance of Staticman. Decided to roll out a PFHub dedicated Staticman hosted on the free tier of Heroku. Hopefully, this will be more stable going forward. Also, will give us more flexibility to adjust the way Staticman works and more easily interact with out Python backend app.
Currently using this version of staticman.
These changes can be viewed live.
Remember to tear down the live site when merging
or closing this pull request.
This change is