I’m curious if anyone is doing anything different in regards to populating Meteor.settings (besides supplying a settings.json) or just storing keys elsewhere?
Specifically I’m looking to store my API keys and other bits of info per-instance info somewhere outside of a settings.json. AWS recently released the AWS Secrets Manager which I find intruiging. I’m just not sure how that would work with Meteor (in that Meteor.settings needs to be loaded on startup or via environment variable).
Anyone doing anything interesting like this?