Skip to content
This repository has been archived by the owner on Sep 26, 2022. It is now read-only.

Manage how the HTTP API is run #191

Open
sr-gi opened this issue Aug 5, 2020 · 0 comments
Open

Manage how the HTTP API is run #191

sr-gi opened this issue Aug 5, 2020 · 0 comments
Labels
enhancement New feature or request
Milestone
v0.2.0

Comments

@sr-gi
Copy link
Member

sr-gi commented Aug 5, 2020

Once #187 is merged, the HTTP API will be handled by gunicorn instead of using the non-production-ready flask webserver.

This is an improvements over the previous approach, but may not be good for all cases. We should give a bit of flexibility about how a user wants to run this.

Add some config options that allow users to choose how they would like to run this.

Check #187 (comment) and #187 (review)
@sr-gi sr-gi added the enhancement New feature or request label Aug 5, 2020
@sr-gi sr-gi mentioned this issue Aug 7, 2020
Merged
@sr-gi sr-gi modified the milestones: v0.1.1, v0.2.0 Sep 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
v0.2.0
Development

No branches or pull requests
1 participant
@sr-gi