Production deployment of kinto-server with Docker
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 437
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 15
Description
Hello,
A sincere appreciation to the entire kinto team for this wonderful and brilliant solution! **Kinto** truly rocks!!!
It was mentioned in the documentation that **uwsgi** is the preferred way to run kinto in production, as it could be deployed behind a proxy server (e.g. nginx).
[Kinto Local Server](https://kinto.readthedocs.io/en/latest/commandline.html#local-server), ```kinto start ...``` was discouraged as not production ready, (maybe due to *pserve*'s limitation facing the internet directly or something). However, the Docker image uses, ```kinto start```, and it appears that's the only way to run kinto server on docker or other orchestrators.
So, is it technically (performance wise) possible to deploy kinto with the following configuration, as an alternative to the uwsgi, in production? Viz:
**nginx** --proxy--> **kinto start . . .** instances (scaled by **supervisord**, or any docker orchestrator)
Thanks, please.
Foluso.
Contributor guide
Research direction
Start with the Docker image configuration and the Local Server and deployment documentation, then compare the documented uwsgi path with the image's kinto start entry point. Done means establishing whether the nginx-proxied, scaled setup is supported for production and recording the supported deployment guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx, python
- Domain
- devops, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100