You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
We need to find an efficient way for Beast to deploy challenges on multiple servers provided efficiently while being deployed on the main server.
The text was updated successfully, but these errors were encountered: