Log files
Right now it automatically saves the command output into a text file, but it wouldn't need to since you can always use a pipe to to that like "abcd buid > build.log" or "abcd build | tee build.log".
Build config file
An optional hidden yaml/json file ".digger" or ".abcd" that would have some information for the CLI such as the build type and platform ("andoid" and "gradle" for example) in the future this could also specify a different build version or path to use.
Setup command
A setup command to set default configurations "abcd setup" such as default android debug keystore config, android home path, cordova path, etc.
Hello,I was thinking on some enhancements around the CLI usage:Log filesRight now it automatically saves the command output into a text file, but it wouldn't need to since you can always use a pipe to to that like "abcd buid > build.log" or "abcd build | tee build.log".Setup commandA setup command to set default configurations "abcd setup" such as default android debug keystore config, android home path, cordova path, etc.Build config fileAn optional hidden yaml/json file ".digger" or ".abcd" that would have some information for the CLI such as the build type and platform ("andoid" and "gradle" for example) in the future this could also specify a different build version or path to use.Debug flagCommands that start another process (such as "build' or "sign") could use a flag "--debug" which if set to true would output everything into stdout, otherwise would just print the actual command response (for example the build command would output a list of generated APKs). Default value for debug would be true.
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev