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

Refactored service to run on AWS lambda #15

Merged
merged 1 commit into from May 13, 2018

Conversation

Projects
None yet
2 participants
@blakeembrey
Collaborator

blakeembrey commented Apr 5, 2017

Since barely anyone hits it anyway, it barely needs the DigitalOcean instance in charge of keeping it up today.

@blakeembrey

This comment has been minimized.

Show comment
Hide comment
@blakeembrey

blakeembrey Apr 5, 2017

Collaborator

I also checked in the Terraform state files, not sure if there's a better open source approach for managing that. If there's a preferred deployment strategy to AWS Lambda, let me know, I've just been doing it with Terraform for a few months now.

Collaborator

blakeembrey commented Apr 5, 2017

I also checked in the Terraform state files, not sure if there's a better open source approach for managing that. If there's a preferred deployment strategy to AWS Lambda, let me know, I've just been doing it with Terraform for a few months now.

@Whoaa512

LGTM. Maybe add some docs or links about how to deploy this with Terraform.

We've been using serverless at work for Lambda deploys, so I'd need ramp up to get started with Terraform.

@blakeembrey blakeembrey merged commit 591a5a1 into master May 13, 2018

@blakeembrey blakeembrey deleted the aws-lambda branch May 13, 2018

@blakeembrey

This comment has been minimized.

Show comment
Hide comment
@blakeembrey

blakeembrey May 13, 2018

Collaborator

Just merged because I never got around to it and it is active, one day I'd like to come back and review the usage and maybe try serverless. How have you preferred it?

Collaborator

blakeembrey commented May 13, 2018

Just merged because I never got around to it and it is active, one day I'd like to come back and review the usage and maybe try serverless. How have you preferred it?

@Whoaa512

This comment has been minimized.

Show comment
Hide comment
@Whoaa512

Whoaa512 May 15, 2018

Collaborator

Serverless was mainly our default choice because we started using it when there were not a lot of other options. Since then I've not used any other lambda deployment framework/tool to be able to compare properly.

Anecdotally, I like serverless because I know the set of packages & plugins I need to get something deployed quickly.

Collaborator

Whoaa512 commented May 15, 2018

Serverless was mainly our default choice because we started using it when there were not a lot of other options. Since then I've not used any other lambda deployment framework/tool to be able to compare properly.

Anecdotally, I like serverless because I know the set of packages & plugins I need to get something deployed quickly.

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