mirror of
https://github.com/embarklabs/embark.git
synced 2025-01-11 14:24:24 +00:00
de0f02d00a
Previously, templates were in a subdirectory of `packages/embark`. Reorganize them so that they are member packages of the monorepo. This allows them to cleanly depend on other members of the monorepo, e.g. `embarkjs-connector-web3`. It is desirable for the templates, in the context of the monorepo, to specify embark as a dependency, to take advantage of `npx embark test` (and it's a "forward looking" setup re: how we plan to evolve embark). However, if embark were to specify the template packages as dependencies a circular relationship would be introduced, which is [unsupported by Lerna][circular]. Therefore, revise the template generator so that all templates are resolved / fetched at runtime, i.e. `boilerplate`, `demo`, and `simple` are no longer "built-ins" *per se*. This change won't be apparent to embark's users, but it does mean that the template generator won't work (in a production install of embark) if it can't connect to the npm registry, i.e. when the user runs `embark demo` or `embark new [--simple]`. When embark is inside the monorepo, templates are resolved and copied from the yarn workspace rather than being fetched from the registry, which is convenient for development. Also, any template dependencies that are members of the monorepo are linked into the copied template's `node_modules` rather than being installed from the registry, again for convenience. During template generation, remove scripts and dependencies that pertain only to membership in the monorepo; for now, that involves removing embark as a dependency since we're not quite ready for that arrangement to be the default, i.e. outside of the monorepo. Refactor the root scripts so that more of them can consistently be used with Lerna's filter options, e.g. `--scope` and `--ignore`. "Combo" scripts that don't support filtering generally have a `:full` postfix. Flip `clean` and `reset` scripts at the root and in the member packages for consistency re: Lerna's notion of `clean` and embark's notion of `reset`. Have each package run its `reset` script when its `clean` script is invoked (and that's all for now), relying on `lerna clean` to delete packages' `node_modules` in view of how Lerna's topological sorting works. Lift the implementation of `embark reset` into a private package in `packages/embark-reset` and make it a bundled dependency of embark. Packages in `dapps/*` depend on `embark-reset` directly and make use of it with `npx embark-reset` (but only in monorepo context). This removes a "wart" where reboots could show errors when embark's sources aren't already built in `packages/embark/dist`. Users will not notice any difference since `embark reset` works as before, transparently making use of the `embark-reset` package. The only downside to having it be a bundled dependency of embark is that bundled deps have all of their `node_modules` included in the tarball built with `npm pack` (that's why having the templates as bundled dependencies of embark isn't a viable approach). However, `embark-reset` only has one dependency, `rimraf`, which is a tiny module, so the cost seems acceptable. As part of the reorganization, move `test_dapps` into `dapps/tests` and `packages/embark/templates` into `dapps/templates`. Keep the directory names short but revise the package names to facilitate simple filtering with `embark-dapp-*`. Consolidate `.yarnrc` and `.gitignore` and clean up some redundant ignore listings. Scripts run with `--scope embark-dapp-*` use `--concurrency=1` to avoid conflicts that could arise over network ports. The `ci:full` and `qa:full` scripts use `--concurrency=1` in all scopes, for two reasons: resource limitations on Travis and AppVeyor result in slower runs with concurrency >1, and if something fails in those contexts it's easier to see what went wrong when Lerna's output isn't interleaved from a bunch of scripts in `packages/*`. Bump the Lerna version. [circular]: https://github.com/lerna/lerna/issues/1198#issuecomment-442278902
92 lines
3.1 KiB
JavaScript
92 lines
3.1 KiB
JavaScript
module.exports = {
|
|
// default applies to all environments
|
|
default: {
|
|
// Blockchain node to deploy the contracts
|
|
deployment: {
|
|
host: "localhost", // Host of the blockchain node
|
|
port: 8546, // Port of the blockchain node
|
|
type: "ws" // Type of connection (ws or rpc),
|
|
// Accounts to use instead of the default account to populate your wallet.
|
|
// The order here corresponds to the order of `web3.eth.getAccounts`, so the first one is the `defaultAccount`
|
|
/*,accounts: [
|
|
{
|
|
privateKey: "your_private_key",
|
|
balance: "5 ether" // You can set the balance of the account in the dev environment
|
|
// Balances are in Wei, but you can specify the unit with its name
|
|
},
|
|
{
|
|
privateKeyFile: "path/to/file", // Either a keystore or a list of keys, separated by , or ;
|
|
password: "passwordForTheKeystore" // Needed to decrypt the keystore file
|
|
},
|
|
{
|
|
mnemonic: "12 word mnemonic",
|
|
addressIndex: "0", // Optional. The index to start getting the address
|
|
numAddresses: "1", // Optional. The number of addresses to get
|
|
hdpath: "m/44'/60'/0'/0/" // Optional. HD derivation path
|
|
},
|
|
{
|
|
"nodeAccounts": true // Uses the Ethereum node's accounts
|
|
}
|
|
]*/
|
|
},
|
|
// order of connections the dapp should connect to
|
|
dappConnection: [
|
|
"$WEB3", // uses pre existing web3 object if available (e.g in Mist)
|
|
"ws://localhost:8546",
|
|
"http://localhost:8545"
|
|
],
|
|
|
|
// Automatically call `ethereum.enable` if true.
|
|
// If false, the following code must run before sending any transaction: `await EmbarkJS.enableEthereum();`
|
|
// Default value is true.
|
|
// dappAutoEnable: true,
|
|
|
|
gas: "auto",
|
|
|
|
// Strategy for the deployment of the contracts:
|
|
// - implicit will try to deploy all the contracts located inside the contracts directory
|
|
// or the directory configured for the location of the contracts. This is default one
|
|
// when not specified
|
|
// - explicit will only attempt to deploy the contracts that are explicitly specified inside the
|
|
// contracts section.
|
|
//strategy: 'implicit',
|
|
|
|
contracts: {
|
|
// example:
|
|
//SimpleStorage: {
|
|
// args: [ 100 ]
|
|
//}
|
|
}
|
|
},
|
|
|
|
// default environment, merges with the settings in default
|
|
// assumed to be the intended environment by `embark run`
|
|
development: {
|
|
dappConnection: [
|
|
"ws://localhost:8546",
|
|
"http://localhost:8545",
|
|
"$WEB3" // uses pre existing web3 object if available (e.g in Mist)
|
|
]
|
|
},
|
|
|
|
// merges with the settings in default
|
|
// used with "embark run privatenet"
|
|
privatenet: {
|
|
},
|
|
|
|
// merges with the settings in default
|
|
// used with "embark run testnet"
|
|
testnet: {
|
|
},
|
|
|
|
// merges with the settings in default
|
|
// used with "embark run livenet"
|
|
livenet: {
|
|
},
|
|
|
|
// you can name an environment with specific settings and then specify with
|
|
// "embark run custom_name" or "embark blockchain custom_name"
|
|
//custom_name: {
|
|
//}
|
|
};
|