how to keep in sync with dapp-offer-up?

[dckc]

PR #6 inherited...

• support for starting a local chain a la yarn start:docker in dapp-offer-up
• something like yarn start:contract (cf yarn start to aggregate all the start-up steps dapp-offer-up#5 )
• add endo resolutions to control bundle size (cf 'request body too large' at yarn start:contract after modifying provided contract dapp-offer-up#28 )
• test that bundle size didn't blow up (cf Test that compressed contract bundles are less than 1MB dapp-offer-up#36 )

But maintaining this dapp independently from dapp-offer-up means addressing these issues in both repositories:

• test that the chain is available before using it (cf test that the chain is available before using it dapp-offer-up#27 )
• test that contract got deployed (cf test that start:contract results in an offerUp instance in agoricNames dapp-offer-up#46 )
• handle out-of-IST (cf silent failure on insufficient IST when installing bundles dapp-offer-up#60 )
• clean up log output (cf output of yarn start:contract is disorganized, not checked dapp-offer-up#62 )

More along those lines, not directly related to contract deployment (perhaps belongs in a separate issue)

• yarn 4: sync with documentation repo on yarn 4 dapp-offer-up#40
• ci: ci for getting started with dapp-offer-up, docker-compose dapp-offer-up#48

[dckc]

#6 copied the yarn start:contract stuff from dapp-agoric-basics.

I'll re-scope this to managing the remaining duplicate work.

[dckc]

Agoric/dapp-offer-up@142bf9a is another bit of dapp-offer-up that should be here.

[dckc]

bundle size test refinement is not in dapp-offer-up

dapp-agoric-basics/contract/test/test-build-proposal.js

Lines 64 to 65 in f48420e

	// JSON RPC hex encoding doubles the size
	t.assert(sizeInMb * 2 < 1, 'Compressed bundle is less than 0.5MB');

https://github.com/Agoric/dapp-offer-up/blob/5a3999fb8e38a6c940a8de5b7a664d994bb0e010/contract/test/test-build-proposal.js

[dckc]

@Jovonni told me an interesting idea yesterday: both of these apps could be forks of a template dap and as refinements are made to the template they can be merged into the daps

[Jovonni]

Things we may need to figure out:

• what repo/branch would serve as the foundational template (some dapps needs to be upgraded)
• which parts of the code belongs in the template repo vs the child repo

This will help us figure out the git strategy, what to rebase to, etc. Might need a design doc run before the work though.