Settings access is doing it wrong

[deanrad]

The idea is that each setting has a key, and the correct settings file (or JSON) is passed in at process startup time, so your code would only contain

Meteor.settings.public.meta.title

not

Meteor.settings[Meteor.settings.environment].public.meta.title

It's seldom that production and dev settings ought to be in the same file anyway, since you don't want to check in prod settings to source control anyway.

[ryw]

@chicagogrooves i agree.
@nickw you agree too? you committed this version...

[nickw]

Yeah this was never fully implemented and was still in the experimentation phase. @chicagogrooves feel free to open a PR.

[deanrad]

groovy, thanks! Sorry if that was a bit