-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#91] Fix: Move database migration right after the database initializing #94
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with a small suggestion
return fmt.Sprintf("postgres://%s:%s@%s:%s/%s?sslmode=disable", | ||
viper.GetString("db_username"), | ||
viper.GetString("db_password"), | ||
viper.GetString("db_host"), | ||
helpers.GetStringConfig("db_port"), | ||
helpers.GetStringConfig("db_name"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we take this chance to drop the use of config/app.toml
file? And change to use .env
files instead.
With that file, we will get confused when adding new environment variables, as we don't know where we should put them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this PR is opened for so long, let's do it in another PR. I've created an issue to do it 🙇🏼
Resolve #91
What happened 👀
Move the database migration right after the database is initialized, just like we did in Varun API project
Insight 📝
N/A
Proof Of Work 📹
All test passed