bitter veldt
I wanna know about best practices providing db credentials to a go project. I don't wanna hardcode the database URI. I'm using goose package in order to run migrations just in case there is a tool that combines with goose in order to define the db string URI (sqlboiler, maybe)
Thank you in advance
proven furnace
use environment variables
(really complex example how I streamlined most of my configuration needs: https://github.com/jxsl13/twstatus-bot)
bitter veldt
(really complex example how I streamlined most of my configuration needs: https:...
First of all thank you for the reply, I'm a noobie in go so I might be wrong, I checked out your repo and I saw that you are hardcoding some of the db config variables like user, port,db name... (main.go). That's exactly what I want to skip, so I guess that as you pointed out I should stick to en variables
proven furnace
I'm not hardcoding them, I am providing defaults
that can be overwritten by cli flags, environment variables or by a config file passed either by a special environment variable or passed by the -c or --config cli flag
most of the time you will use the same database port
but might want to change the database host/ip
(the complex stuff happens in config/koanf.go)
sane defaults allow you to reduce the size of yout configuration.
In my case, a user would only need to care about half of my configuration options because the rest of them has a sane default value:
