Meteor 1.4 Settings API: alert thresholds frozen at startup after moving off --settings files
Context Since Meteor 1.4 replaced the deprecated --settings file loading with the enhanced Settings API, Meteor.settings is loaded once at server startup and is immutable at runtime. Attempts to assign new values to it silently have no effect until the server restarts. Goal I want to drive alerting thresholds (for example, error-rate or queue-depth limits) f