Noted that ReadInConfig returns errors that can be handled

This commit is contained in:
Kiril Zvezdarov 2015-03-28 13:43:38 -04:00
parent 40762f7541
commit 39ab3ca72e
1 changed files with 4 additions and 1 deletions

View File

@ -74,7 +74,10 @@ currently a single viper only supports a single config file.
viper.SetConfigName("config") // name of config file (without extension) viper.SetConfigName("config") // name of config file (without extension)
viper.AddConfigPath("/etc/appname/") // path to look for the config file in viper.AddConfigPath("/etc/appname/") // path to look for the config file in
viper.AddConfigPath("$HOME/.appname") // call multiple times to add many search paths viper.AddConfigPath("$HOME/.appname") // call multiple times to add many search paths
viper.ReadInConfig() // Find and read the config file err := viper.ReadInConfig() // Find and read the config file
if err != nil { // Handle errors reading the config file
panic(fmt.Errorf("Fatal error config file: %s \n", err))
}
### Setting Overrides ### Setting Overrides