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

Implement distributed challenges deployment and management #363

Open
sukhman-sukh opened this issue Dec 18, 2024 · 1 comment · May be fixed by #377
Open

Implement distributed challenges deployment and management #363

sukhman-sukh opened this issue Dec 18, 2024 · 1 comment · May be fixed by #377
Labels
enhancement New feature or request

Comments

@sukhman-sukh
Copy link
Contributor

We need to find an efficient way for Beast to deploy challenges on multiple servers provided efficiently while being deployed on the main server.

@sukhman-sukh sukhman-sukh added the enhancement New feature or request label Dec 18, 2024
@sukhman-sukh
Copy link
Contributor Author

One of the ways could be to deploy Beast on a server and specify available machines' access points in the beast.toml (globally). Implement a load balancer inside Beast and store it in Redis for fast lookup of challenges and their deployed address. Redirect the request to the deployed address from the proxied main server, but we would need to do this efficiently to handle large load.

@sukhman-sukh sukhman-sukh linked a pull request Feb 4, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant