Hope the question is not too OT for this group, if yes please just ignore it and forgive me.
We're in the progress of migrating a somewhat-complex application (https://github.com/evcc-io/evcc) from static, yaml-based configuration to fully UI-controllable dynamic config. A running application manages some 5-20 configurable objects. Using yaml, config was just public properties of structs manages by yaml.Unmarshal. We could continue doing so and maybe use json.(Un)Marshal to put the identical structs into a database table, but it feels odd to have public properties in objects/structs just for the purpose of storing an manipulating their configuration. What are good patterns for managing runtime config and is there any project you can recommend to look at that does this particularly well or elegant? Thanks, Andi -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/8a218694-a309-458c-89b5-724a4610017fn%40googlegroups.com.
