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.

Sign up for GitHub

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

Jump to bottom

AWS Lambdaify #2

Open

AnEmortalKid opened this issue Feb 6, 2019 · 1 comment

Assignees

Member

AnEmortalKid commented Feb 6, 2019

This currently lives in heroku, but I think we could make this function a lambda and have it in AWS or some openfaas system.

AnEmortalKid changed the title ~~Lambdaify~~ AWS Lambdaify

Member Author

AnEmortalKid commented Apr 4, 2019

We do some funky stuff to load the latest version (look at dogescript:fetch), we could potentially require the dogescript lib as it were an npm package: https://medium.com/@jonchurch/use-github-branch-as-dependency-in-package-json-5eb609c81f1a

Might not need the hook if we wire things in lambda (https://chatbotslife.com/write-a-serverless-slack-chat-bot-using-aws-e2d2432c380e) so that the function gets re-created with a fresh instance that we can npm install on.

The current setup uses a deploy-bot.js script https://github.com/dogescript/dogescript/blob/master/deploy-bot.js#L7 that's wired to heroku, to re-start the web dyno. That dyno, on initialization does all the npm link / unlink stuff it needs + gathering of the hash.

AnEmortalKid mentioned this issue

move test dep / update bot deps dogescript/dogescript#209

Merged

AnEmortalKid self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment