use of JSON configuration?

[JamesClonk]

Because of complications with the current environment variable based configuration (see #2) a better solution might be to implement a JSON based configuration?
Either read entirely from an new env var BACKMAN_CONFIG, and/or provided as config.json together with the app during push?

• Investigate using JSON env var BACKMAN_CONFIG.
  • Will it work without escaping issues?
• Investigate fallback loading local file config.json
• Investigate backwards-compatible fallback to parsing old env vars too?

---

Pros:

• Easier handling of more complex configuration scenarios
• Future proof

Cons:

• Reconfiguring a deployed app on the fly might get more time consuming (adjusting 1 big config env var instead of just multiple more simpler & smaller ones)

[JamesClonk]

implemented new JSON configuration format