-
Notifications
You must be signed in to change notification settings - Fork 76
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
soroban-rpc: deploy public instance on futurenet #418
Comments
Are we sure this is a good precedent to set? I'd rather see deployments be as simple and streamlined as possible. |
for stop gap, @leighmcculloch helped out, and did a short term deployment of quickstart(soroban-rpc enabled) on Digital Ocean: |
Ops ticket for reference: |
k8s manifest for the deployment is up for review. coordinating with ops for next steps on stellar/ops#2165 discussion |
the manfiests for prd deployment up for review - https://github.com/stellar/kube/pull/1337 |
@sreuland @tomerweller Do we need stellar-futurenet.4d63.com/ anymore? |
no. we have rpc-futurenet.stellar.org |
@tomerweller Should we add this to CLI? Have a special |
@willemneal yes I like that idea! |
What problem does your feature solve?
We'd like to facilitate more engagement/usage of RPC in the ecosystem prior to launching on testnet. We eventually plan to host a public instance on testnet as well, but not pubnet.
What would you like to see?
A deployed public instance of soroban-rpc on futurenet on stellar domain,
rpc-futurenet.stellar.org
. Deployment should be integrated into the soroban release process so that it receives updates appropriately.Initial deployment to use k8s and the quickstart soroban-dev image for soroban rpc, and ingress route for dns.
This initial deployment will later be refactored to use new rpc service deployment image from #382 and updated helm chart to use/config that image.
What alternatives are there?
The text was updated successfully, but these errors were encountered: