1.3.4
- The exit code for
mup validateis now 1 when there are validation errors - Fix changing proxy's clientUploadLimit with
proxy.shared.clientUploadLimit - Added a
--scruboption tomup validate, which when used with--showshows the config with most of the sensitive information removed mup mongo logsaccepts the same options asmup logsand other log commands- Use npm-shrinkwrap to prevent #757 from happening again
- Hide docker error when trying to roll back and checking if an image exists. It is handled and normal, but could be confused with the reason for the app failing to start
Plugins and Hooks
- Building the app (but not archiving it) was moved to a new command
meteor.build, which is run bymeteor.deployandmeteor.push. This allows plugins or hooks to modify the bundle before it is archived and uploaded to the servers. - Plugins can export a
scrubConfig(config, utils)function, which should return the config with all sensitive information removed api.scrubConfig()was added, which returns the config after modified by anyscrubConfigfunctions from pluginsapi.validateConfigonly shows the errors on the console the first time it is runMODULE_NOT_FOUNDerrors are now shown when a plugin fails to load due to being unable to resolve a module
Docs
- Color, font, and spacing changes were made to the docs. It should look nicer and be easier to read.
- Fixed grammer and capitalization
- Many example configs in the docs are validated with
mup validate - Many example configs show more of the config surrounding the section being documented