mycryptohq / drawbridge Goto Github PK

constants contains MyCrypto specific configs that should be removed before a production release (npm)

Instead of hardcoding support for beta / production / staging in the codebase, allow CLI arguments to be based off of the keys (repo envs) specified in .drawbridgerc.

This allows us to support more than 3 environments, and allows us to better model the environment model in drawbridge.

we can infer origin branch instead of redundantly specifying in another argument.

--betaBranch, --prodBranch, etc can become --originBranch since we can infer origin value from push beta to prod

[ISSUE DESCRIPTION TBD]

Other projects using the app may need additional build-time dependencies than we've specified in the Dockerfile that ships with drawbridge. Allow a custom Dockerfile to be specified in config.

In some cases, we (and presumably other future users of drawbridge) will issue releases from the same repo, but to another branch (i.e. gh-pages).

A more robust implementation that supports same-repo releases should be designed and implemented

Documentation does not describe all use cases or features.

Adjust build process to target NPM as a CLI app.