webhook driven heroku (re)deployment_G

[BrianClement]

[Issue originally created 2017-Mar-26 00:01:50 UTC by hammockman]

When changes are made to the discviewapi code in this repo they need to be deployed to heroku.

Automate this using github's webhook mechanism.

[BrianClement]

[Comment originally created 2017-Mar-26 00:07:00 UTC by hammockman]

There is a now a very simple web app handling a push event triggered webhook.

Some notes:

• Currently this app is running on an AWS server (belonging to JH). This is not a long term solution.
• All push-es will result in redeployment. As yet no attempt is made to restrict heroku (re)deployment to changes to discviewapi only.
• No attempt is made to check the status of the heroku app at the end of the process.
• The app is very fragile.

[BrianClement]

[Comment originally created 2017-Mar-26 22:03:47 UTC by racleave]

Does this mean we should remove the committorootanddiscviewapi.sh script? Or leave it for now and not use it until we are happy with the webhook solution (at which point we can remove the script and modify the discviewapi README.md)

[BrianClement]

[Comment originally created 2017-Mar-26 22:33:39 UTC by hammockman]

leave it for the moment.

On Mon, Mar 27, 2017 at 11:03 AM, racleave notifications@github.com wrote:

Does this mean we should remove the committorootanddiscviewapi.sh https://github.com/ScionResearch/discbot-discview/blob/master/committorootanddiscviewapi.sh script? Or leave it for now and not use it until we are happy with the webhook solution (at which point we can remove the script and modify the discviewapi README.md https://github.com/ScionResearch/discbot-discview/blob/master/discviewapi/README.md )

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ScionResearch/discbot-discview/issues/5#issuecomment-289320038, or mute the thread https://github.com/notifications/unsubscribe-auth/AF5opEKYpe9L0R4hAoo7a5q-SRToJipDks5rpuDDgaJpZM4MpQvr .