[go-nuts] app configuration pattern?

On Dec 1, 2014, at 3:52 PM, Tomaz Kovacic wrote:

I'm wondering how do you configure your web apps written in Go for production and development environment. Do you just use YAML files and maintain one with production secrets?

Here's my take on it:
https://github.com/tomazk/envcfg <https://github.com/tomazk/envcfg>

* apps should store configuration in the environment as per manifestos like "12 factor app"
* lib github.com/tomazk/envcfg encourages you to define a struct that'll hold your env variables as fields
* use envcfg.Unmarshal to unmarshal env variables to the object with the type you defined in the struct
* store this object globally and access it when configuring clients and services

Any thoughts?

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.

I'm wondering how do you configure your web apps written in Go for
production and development environment. Do you just use YAML files and
maintain one with production secrets?

Here's my take on it:
https://github.com/tomazk/envcfg

* apps should store configuration in the environment as per manifestos
like "12 factor app"
* lib github.com/tomazk/envcfg encourages you to define a struct that'll
hold your env variables as fields
* use envcfg.Unmarshal to unmarshal env variables to the object with the
type you defined in the struct
* store this object globally and access it when configuring clients and
services

Any thoughts?