Skip to content
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

Setup hosting for this image #10

Open
reefdog opened this issue Aug 14, 2019 · 2 comments
Open

Setup hosting for this image #10

reefdog opened this issue Aug 14, 2019 · 2 comments
Assignees

Comments

@reefdog
Copy link

reefdog commented Aug 14, 2019

Let's get this image hosted (on Heroku? Amazon ECS?) so we can interact with it as our query parser endpoint rather than the Lambda invocation.

@slifty
Copy link
Contributor

slifty commented Aug 14, 2019

It looks like Amazon ECS is the mechanism for hosting docker containers on AWS; I'm going to look into what it takes to do correctly and document here.

We may want to consider setting up a VPC (Virtual Private Cloud) so that nobody can directly access / query the docker container, and only the prior art archive's backend has access. However, this would require eventual migration of the entire infrastructure onto AWS so that's not really an option for now.

We can also host this dockerized parser on Heroku which may be the right solution given the way Heroku is the core platform for most of the infrastructure.

@slifty
Copy link
Contributor

slifty commented Aug 14, 2019

The v1 deployment is currently on Heroku; I believe at docker-usptofe

There appears to be a memory leak somewhere in the application

image

I want to confirm my understanding of the deployment before spinning this out into its own issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants