creating-contract-agnostic-docker --WIP--

[amessbee]

This is a twin of a PR in dapp-offer-up repo.

Goal of this PR is to (maybe partially) close #92. Currently running of agoriclocal chain and deploying and starting contract are intertwined in this dapp. This is somewhat unnatural as chain should not depend on the files of any specific contract - apart from the ones that designated essential for its running.
Further, running a chain independent of a specific contract will allow testing of multiple dapp simultaneously running and interacting with each other which may unlock several scenarios that a developer may want to test for.

As per discussion with @toliaqat, here is a plan:

• docker compose file should not mount the contract directory as a volume. Rather it should mount (ideally) a single script (run-chain.sh) that necessary tasks for running of chain independently.
• run-chain.sh should do just that - run the chain and nothing else!

yarn start:contract should handle most of the heavy work including:

• setup a dedicated workspace for the contract (dapp-offer-up here)
• copy tools needed for building, i.e., Makefile
• copy scripts and tools needed for required for making install-bundle, submit-proposal, vote etc. calls.
• create contract bundles on host machine, and then copy them to the workspace in docker container.
• make install-bundle, submit-proposal, vote etc. calls needed to deploy and run the contract using scripts as before.
• update relevant docs. In particular, add guides to install agoric and agd CLI.

Link to IBIS document.

[amessbee]

@mujahidkay @rabi-siddique @frazarshad @usmanmani1122 @Muneeb147 Need your help to review and test the following on your machines and get feedback. Testing two dapps in tandem can be done as below:

• checkout both this PR and the twin in dapp-offer-up.
• Do the usual in one of the repo ( yarn install, yarn start:docker, yarn start:contract, yarn start:ui ) make sure everything runs as expect. Do not quite UI.
• In the second repo, do everything usual but do not run yarn start:docker (it should fail to run if you try it). Everything should run as expected.
• Once you have both UI's up and running, you should be able to interact with both of them simultaneously and see the effect in the other. For example, you can buy map and scroll in offer-up dapp, and then exchange them for some BLD in SWAP of dapp-agoric-basics. Let me know if you run into any issues.

[dckc]

interesting approach!

[dckc]

idea: to manage namespace collisions, use an env variable with a default ${AG_CONTAINER:-agd}

and maybe for ws-agoric-basics