Skip to content
This repository has been archived by the owner on Jun 29, 2023. It is now read-only.

Deploy to Goerli tesnet #582

Open
jacque006 opened this issue May 4, 2021 · 3 comments · May be fixed by #646
Open

Deploy to Goerli tesnet #582

jacque006 opened this issue May 4, 2021 · 3 comments · May be fixed by #646
Assignees

Comments

@jacque006
Copy link
Collaborator

  • Deploy contracts to Goerli testnet
  • Determine where to host nodes (AWS, DO, own machines, etc.)
  • Setup CI pipeline to allow for easy deploy of new updates to contracts and nodes.
  • Determine initial testnet seed state
@jacque006 jacque006 added this to the Public Testnet milestone May 4, 2021
@jacque006
Copy link
Collaborator Author

jacque006 commented Jun 28, 2021

@ChihChengLiang When would we want to trigger an update to this public testnet? I can see doing it either on merges to master or on releases. On master merges would lead to more frequent updates but could be unstable/bug riddled, whereas releases will keep things more stable but have less updates.

We could have two different contract/node deployments, one off of master and another off of releases. The unstable master one would be very similar to the internal dev net we have now.

We could also try a hybrid approach, something like:

  • Releases deploy contract changes, as well as update stable node(s).
  • master merges update unstable node(s)

@ChihChengLiang
Copy link
Collaborator

I'm slightly leaning toward a trigger at release. When we redeploy there are usually minor or trivial bugs to investigate or fix, which might be annoying to fix frequently.

But all the approaches sound good to me.

@jacque006
Copy link
Collaborator Author

jacque006 commented Jul 28, 2021

Rather than managing our dev testnet on a VM, consider as part of this work automating updates to the dev testnet using a CI/CD pipeline as well. Can push updates on merges to master.

If this increases scope too much, break off into another issue.

@jacque006 jacque006 self-assigned this Aug 4, 2021
@jacque006 jacque006 linked a pull request Aug 9, 2021 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants