-
Notifications
You must be signed in to change notification settings - Fork 3
Config: Need a modular config system. THIS IS READY. See PR LINK in this issue #620
Comments
https://pkg.go.dev/go.uber.org/config They use this in their m3 project: https://github.com/m3db/m3 It allows you to have the config split into many files at design time, which we need because of the Modules needing only the config for them and so they can run example. Then at build time it compacts them into one config file. So it seems perfect for us as its designed for a Modular decoupled architecture like ours is. At build time,We can suck up all the separate configs of each module into one config. At runtimeWe need maintemplate to load the config and hand the config data to sys-core don't forget. I think this is good enough. I did not have time to try this out though. Joe, if you get time make an example for the devs !! |
sys-config: working makefile added #620
Hey @cloudwebrtc and @WinWisely268 The PR above solves: here it is: #623 You can run the make file to see how it works and in the PR i explain how we apple it to maintemplate2 and sys-core and any modules we use it with. |
sys-core boost it up and hands the pointer to each Module so they can access theie data.
The model that describes each Modules server config needs to be in each Module.
The on disk JSON or YAML needs to live at maintemplate level of course because that is where the server boots up from.
SO he JSON file will look a bit like this semantically.
The text was updated successfully, but these errors were encountered: