Idea for Configuration/Environment

[jfmario]

I'm curious how the following idea of environment and configuration comports with yours.

Users define structs called <Something>Config in config/ like so:

type DbConfig struct {
    DbUrl string `env:"DB_URL" envDefault:"postgres:postgres@localhost:5432/postgres"`
}

type CacheConfig struct {
    CacheDriver string `env:"CACHE_DRIVER" envDefault:"redis"`
    RedisHost string `env:"REDIS_HOST" envDefault:"localhost"`
    RedisPort int `env:"REDIS_POST" envDefault:"6379"`
}

This example in the bud documentation uses github.com/caarlos0/env/v6 to show a way to do env, but if leaning on this library is a problem then bud could implement a similar API. Either way, the following is what I propose that bud do:

Users can specify these config structs as dependencies of controllers, etc. If they do, bud satisfies the dependencies according to its normal DI system with the following two additions:

• Bud ensures that the .env file is read into the OS environment using github.com/joho/godotenv.
• Bud calls env.Parse(e) if using "github.com/caarlos0/env/v6", or some similar thing to inject any OS environment values into the config objects (prior to adding them to the controller)

Let me know if this seems correct and/or feasible.