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
Instead of working in a custom deploy flow for our own development environment for Aragon apps, we should generalize this at the aragon-dev-cli level to setup a complete environment.
$ aragon-dev-cli setup [--registry-name Domain name for registry (default: aragonpm.test)]
Steps needed:
Deploy an ENS instance a create the needed subnodes until registryName is owned by the sender.
Deploy an APM instance with the rootnode for registryName. Call apm.setResolver().
This migration file for APM where all this steps are performed can be used for reference.
We need a way to save both the ENS and the registry name so that following aragon-dev-cli executions automatically use them (maybe add them to a config file that gets read if no flags are provided?).
The text was updated successfully, but these errors were encountered:
Instead of working in a custom deploy flow for our own development environment for Aragon apps, we should generalize this at the
aragon-dev-cli
level to setup a complete environment.Steps needed:
registryName
is owned by the sender.registryName
. Callapm.setResolver()
.This migration file for APM where all this steps are performed can be used for reference.
We need a way to save both the ENS and the registry name so that following
aragon-dev-cli
executions automatically use them (maybe add them to a config file that gets read if no flags are provided?).The text was updated successfully, but these errors were encountered: