diff --git a/apps/cic-eth/admin_requirements.txt b/apps/cic-eth/admin_requirements.txt index 4e9b1a16..cd9fcc74 100644 --- a/apps/cic-eth/admin_requirements.txt +++ b/apps/cic-eth/admin_requirements.txt @@ -1,5 +1,5 @@ SQLAlchemy==1.3.20 -cic-eth-registry>=0.6.1a3,<0.7.0 +cic-eth-registry>=0.6.1a6,<0.7.0 hexathon~=0.0.1a8 chainqueue>=0.0.4a6,<0.1.0 eth-erc20>=0.1.2a2,<0.2.0 diff --git a/apps/cic-eth/services_requirements.txt b/apps/cic-eth/services_requirements.txt index bc929ed8..bd44e17f 100644 --- a/apps/cic-eth/services_requirements.txt +++ b/apps/cic-eth/services_requirements.txt @@ -8,7 +8,7 @@ pycryptodome==3.10.1 liveness~=0.0.1a7 eth-address-index>=0.2.3a4,<0.3.0 eth-accounts-index>=0.1.2a3,<0.2.0 -cic-eth-registry>=0.6.1a5,<0.7.0 +cic-eth-registry>=0.6.1a6,<0.7.0 erc20-faucet>=0.3.2a2,<0.4.0 erc20-transfer-authorization>=0.3.5a2,<0.4.0 sarafu-faucet>=0.0.7a2,<0.1.0 diff --git a/apps/cic-eth/tools_requirements.txt b/apps/cic-eth/tools_requirements.txt index 401bdc8b..e4085ff9 100644 --- a/apps/cic-eth/tools_requirements.txt +++ b/apps/cic-eth/tools_requirements.txt @@ -1,6 +1,6 @@ crypto-dev-signer>=0.4.15a7,<=0.4.15 chainqueue>=0.0.5a1,<0.1.0 -cic-eth-registry>=0.6.1a3,<0.7.0 +cic-eth-registry>=0.6.1a6,<0.7.0 redis==3.5.3 hexathon~=0.0.1a8 pycryptodome==3.10.1 diff --git a/apps/contract-migration/README.md b/apps/contract-migration/README.md index 59b01853..baf025aa 100644 --- a/apps/contract-migration/README.md +++ b/apps/contract-migration/README.md @@ -1,53 +1,3 @@ -# Contract Migration +# System bootstrap scripts -Common docker artifacts and bootstrap scripts - -## How this repo works - -This repo builds contracts and deploys them to a chain - -First, bring up an eth evm provider -``` -docker-compose up eth -``` - -Now build this repo's image and run it against the 'eth' service (ganache, for example). You will need to bind to the docker-compose network (cic-network) and mount the special contract output folder that dependent services use to get deployed contract addresses. - -Here is how to do that in one shot: -``` -docker build -t registry.gitlab.com/grassrootseconomics/cic-docker-internal -f docker/ . && docker run --env ETH_PROVIDER=http://eth:8545 --net cic-network -v cic-docker-internal_contract-config:/tmp/cic/config --rm -it registry.gitlab.com/grassrootseconomics/cic-docker-internal reset.sh -``` - -Stop the containers and bring down the services with -``` -docker-compose down -``` - -If you want a fresh start to the dev environment then bring down the services and delete their associated volumes with - -``` -docker-compose down -v -``` - -A goal is to go through all of these containers and create a default non-root user a la: -https://vsupalov.com/docker-shared-permissions/ - -## Tips and Tricks - -Sometimes you just want to hold a container open in docker compose so you can exec into it and poke around. Replace "command" with - -``` - command: - - /bin/sh - - -c - - | - tail -f /dev/null -``` -then - -``` -docker exec -it [IMAGE_NANE] sh -``` - ---- diff --git a/apps/contract-migration/README_bloxberg.md b/apps/contract-migration/README_bloxberg.md new file mode 100644 index 00000000..59b01853 --- /dev/null +++ b/apps/contract-migration/README_bloxberg.md @@ -0,0 +1,53 @@ +# Contract Migration + +Common docker artifacts and bootstrap scripts + +## How this repo works + +This repo builds contracts and deploys them to a chain + +First, bring up an eth evm provider +``` +docker-compose up eth +``` + +Now build this repo's image and run it against the 'eth' service (ganache, for example). You will need to bind to the docker-compose network (cic-network) and mount the special contract output folder that dependent services use to get deployed contract addresses. + +Here is how to do that in one shot: +``` +docker build -t registry.gitlab.com/grassrootseconomics/cic-docker-internal -f docker/ . && docker run --env ETH_PROVIDER=http://eth:8545 --net cic-network -v cic-docker-internal_contract-config:/tmp/cic/config --rm -it registry.gitlab.com/grassrootseconomics/cic-docker-internal reset.sh +``` + +Stop the containers and bring down the services with +``` +docker-compose down +``` + +If you want a fresh start to the dev environment then bring down the services and delete their associated volumes with + +``` +docker-compose down -v +``` + +A goal is to go through all of these containers and create a default non-root user a la: +https://vsupalov.com/docker-shared-permissions/ + +## Tips and Tricks + +Sometimes you just want to hold a container open in docker compose so you can exec into it and poke around. Replace "command" with + +``` + command: + - /bin/sh + - -c + - | + tail -f /dev/null +``` +then + +``` +docker exec -it [IMAGE_NANE] sh +``` + +--- +