We should sync on how the setup bundling might work for a "bootcamp in a box" type of approach.
I've laid down some general ideas, such as:
"How to conduct the bootcamp" docs: setup/README.md
Cargo workspace (Cargo.toml
):
[workspace]
members = [
"quest-1/**/*",
"quest-2/**/*",
"quest-3/**/*",
"quest-4/**/*",
"quest-5/**/*",
"quest-6/**/*",
"quest-7/**/*",
]
Node scripts to create assets (setup/package.json
):
"scripts": {
"build": "ncc build ./src/index.ts --out dist/",
"create-cannons": "node dist/index.js --spl 120",
"create-compasses": "node dist/index.js --spl 60",
"create-fishing-nets": "node dist/index.js --spl 60",
"create-gold": "node dist/index.js --spl 10000",
"create-grappling-hooks": "node dist/index.js --spl 60",
"create-gunpowder": "node dist/index.js --spl 160",
"create-kraken": "node dist/index.js --nft 1",
"create-muskets": "node dist/index.js --spl 80",
"create-rum": "node dist/index.js --spl 200",
"create-telescopes": "node dist/index.js --nft 30",
"create-treasure-maps": "node dist/index.js --nft 30",
"create-trophies": "node dist/index.js --nft 10"
}
This is just a start, but we can probably align to make sure this thing actually works out-of-the-box, and we can even align on this after the bootcamp is over, maybe.