New page: better configuration

[novalagung]

New page: better configuration

[bokunodev]

Json is already used for configuration files in many Go programs. Json is "simple" and "readable".
also to use Json no external dependencies required.
If it's not Json, then what is the alternative?
I suggest .ini file as an alternative

[novalagung]

@bokunodev

JSON is not recommended on the production stage, especially when application managed using orchestration via Kubernetes. Every configuration needs to be in an os environment variable or in the shared storage like ETCD for example.

It'll be hard to manage the app seamlessly in an automated manner when the config is stored in a file. Like for example, what if I want to scale the current container into several instances with different port and config? I need to rewrite the .ini or the .json file on-the-fly? No. definitely nope.

I'm not talking about the self-preference version. I'm talking about real-world implementation. even docker-compose used env var to manage the config

[novalagung]

what I'm going to do probably improve the current JSON config chapter, explain the pros and cons (from DevOps perspective). and then create another one that uses OS env var. let's see.