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
Is your feature request related to a problem? Please describe.
This is not a direct problem, but some tweaks can make it far more flexible to setup. This has been discussed in #36 but should also be very easy for single chain.
Describe the solution you'd like
The proxy should default to "ALL" chains, however, it should be a configuration/environment variable that enables the proxy to run for a smaller subset of chains, or even a single chain. Projects of any size could then move proxies closer to their users in a much simpler manner.
Minimum Resource Requirement Re-evaluation - See Below
Describe alternatives you've considered
N/A
Additional context
This can be done currently by tweaking the hotfix in /proxy/endpoints.py to be != as opposed to == - Can Confirm this works
The minimum proxy resources could based on a flat amount (for core docker/resources) and then be set on a per-chain basis.
Example X + NY where X = Base Resources of 1 vcpu and 1 gb memory and then Y requires 0.25 vcpu and 0.25gb memory and N is number of chains being setup on a given proxy
Internal Proxy usage for projects or smaller dApps should be able to leverage the smallest compute resource possible to attain a self-hosted proxy while larger projects and multi-SKALE Chain projects would require more resources.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This is not a direct problem, but some tweaks can make it far more flexible to setup. This has been discussed in #36 but should also be very easy for single chain.
Describe the solution you'd like
The proxy should default to "ALL" chains, however, it should be a configuration/environment variable that enables the proxy to run for a smaller subset of chains, or even a single chain. Projects of any size could then move proxies closer to their users in a much simpler manner.
Minimum Resource Requirement Re-evaluation - See Below
Describe alternatives you've considered
N/A
Additional context
Example X + NY where X = Base Resources of 1 vcpu and 1 gb memory and then Y requires 0.25 vcpu and 0.25gb memory and N is number of chains being setup on a given proxy
The text was updated successfully, but these errors were encountered: