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
It's difficult to debug issues our partners run into when deploying nitro. We should have a reference for deploying nitro on top of our Espresso sequencer cloud deployments. It does not need to be a persistent deployment immediately because we don't strictly need or want to run a persistent deployment ourselves.
If we can provide this we can
identify issue nitro operators may face earlier and fix them
reduce the chances of misconfiguration because nitro operators have a reference to refer to
A minimal implementation could be a script to generate config files (if necessary), deploy contracts and run the nitro services.
It's difficult to debug issues our partners run into when deploying nitro. We should have a reference for deploying nitro on top of our Espresso sequencer cloud deployments. It does not need to be a persistent deployment immediately because we don't strictly need or want to run a persistent deployment ourselves.
If we can provide this we can
A minimal implementation could be a script to generate config files (if necessary), deploy contracts and run the nitro services.
Cappuccino deployment details are here: https://www.notion.so/espressosys/Cappuccino-Deployment-Info-5ea5e4b000b947859eca326457811843
Deliverables
The text was updated successfully, but these errors were encountered: