mup meteor debugcommand to use a node debugger with your app in production
I am working on the plan for Meteor Up 1.6. The focus will be on simplifying creating a plugin, and making sure all plugins are more consistent in features and behavior. Some additional ideas are:
I would appreciate feedback on which of these are more or less important ,and if there are any other features that should be considered.
Thanks. I should have been more specific about the difficulties: For some apps the env vars, the servers, or other options should be different between channels/environments. For example, you might not want staging to use the same MONGO_URL as production, or you want production to run on 5 servers, and staging to run on a single, separate server. Right now this is solved by using different mup configs. In the other direction, some options must be the same between environments since the builds will be shared (for example, prepare bundle and build options).
About the implementation, I am planning in Mup 1.6 to version the images created by Prepare Bundle instead of always using
previous. Combined with using a private docker registry which will be available in Mup 1.5, this will allow flexibility in what servers are used for what environment/channel.
appsarray, but I haven't decided what the config should be for plugins that require different configuration per app.
DEBUG=mup* mup deploy —verbose
DEBUG=mup* mup deploy —verbose --cached-build