Open jhodges10 opened 6 years ago
:) Thanks for the suggestion. It could be done via AWS Lambda, but I think we're leaning toward using our Jenkins deployment which is more open (e.g. external site and logs are visible publicly).
I believe that @codablock has plans for this in the not-too-distant future, but will let him speak to that (or I could be wrong).
@nmarley Jenkins could work too. As long it's addressed one way or another, I'm happy.
Mostly just wanted an excuse to use a Lambda function and it turns out you can do more with them than I thought!
Another thing we might be able to do is just add a Dockerfile to the core repo, and set to build and push an image upon each release / merge to master
. This is a common pattern in other projects.h
That would let us just remove this repo entirely.
In the past, this repo was slow to be updated and is done manually. This seems both inefficient and leads to delays in propagation of the different installation options on new releases.
Looks like it can all be wrapped up into an AWS lambda function that gets called by a Github deploy Webhook.
The deploy webhook for www.github.com/dashpay/dash would trigger an AWS lambda function which would update this repo.
Here's a link to a gist which covers most of what needs to be done as well as a blog post that goes into further details.