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

Turnkey production deployment #583

Open
patcon opened this issue Sep 22, 2020 · 2 comments
Open

Turnkey production deployment #583

patcon opened this issue Sep 22, 2020 · 2 comments
Labels
👋🏽 community ⚒️ infrastructure Re: automation, continuous integration.
Milestone

Comments

@patcon
Copy link
Contributor

patcon commented Sep 22, 2020

As stated pretty clearly in readme, this repo isn't turnkey.

This thread is to document anything related to making this code more production-ready :)

@patcon patcon changed the title General discussion and link-sharing about future production-ready polis self-hosting General discussion about making self-hosting production-ready Sep 22, 2020
@patcon
Copy link
Contributor Author

patcon commented Sep 22, 2020

@metasoarous in Gitter:

Polis should handle hundreds of participants without breaking a sweat. Getting into the thousands you'll want to make sure you have enough provisioned capacity , both in terms of math worker size (RAM mostly), and number of server nodes handling requests.

@metasoarous metasoarous added this to Priority in Polis Development Dec 2, 2021
@metasoarous metasoarous changed the title General discussion about making self-hosting production-ready Turnkey production deployment Mar 3, 2022
@metasoarous
Copy link
Member

To be clear, the repo itself is production ready (it's already in production in multiple instances around the world). We're even using the Docker infrastructure in production ourselves now. It's really just not the docker-compose infrastructure which is not currently safe for production as it stands. Certainly though, this all implies that deployment is not yet turnkey.

FWIW, I just wrote an extensive description of the current state of deployment infrastructure and roadmap in discussion #1319. As I see it, the work left is:

  • Finish pulling out development artifacts into a separate docker-compose.dev.yml (see use base/prod/dev docker compose files #555)
  • Do a full audit of the current contents of docker-compose.yml to make sure there's nothing there which shouldn't be (and probably do once over on the Dockerfiles to make sure they're in good shape)
  • Ensure configuration is streamlined so that folks aren't tracking down multiple configuration files (see Draft: Feature/convict with config volume #1275)
  • Improve deployment documentation
  • Add load balancing to the docker compose setup

The last step here is necessary for scaling server nodes in order to support larger (and multiple simultaneous) conversations, but is also potentially a lot of work, and so could be split off as a separate issue. I think it's fine to consider this issue as being focused solely on making it relatively easy to set up a secure small deployment using the docker-compose infrastructure. But worth including above for the sake of tracking the broader roadmap.

Thanks

@metasoarous metasoarous added this to the Stable milestone Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👋🏽 community ⚒️ infrastructure Re: automation, continuous integration.
Projects
Development

No branches or pull requests

3 participants