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

Run the registry in multiple threads and use a reverse proxy for forwarding #300

Open
wilzbach opened this issue Mar 23, 2018 · 0 comments

Comments

@wilzbach
Copy link
Member

  • Allows one Vibe.d process to die without affecting the entire website
  • The reverse proxy can detect which upstreams in a pool are currently alive, s.t. the failed instance can restart itself

Ideally Fiber's should be able to crash without affecting the entire process, but well ...

A temporary workaround might be to use code-mirror.dlang.io as a fallback if the main Vibe.d process dies.
Better to display something that just a 502.

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

1 participant