-
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
Dockerize korotagger and automate DB Initialization #1
base: master
Are you sure you want to change the base?
Conversation
Revert https to git
replace image with build directive, remove unecessary cpu and memory limits and leave it up to user to add them back
remove check for my own inserted "config.first_time_run", instead use "member.required_roles" which is the last created table on the third SQL script at migrations
comment out image directive, encourage building instead for the latest builds from repo directly. add double quotes on example postgres password to encourage properly quoting password
wait_for_postgres | ||
|
||
# Check if it is the first time run | ||
if check_first_time_run; then |
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 remove check_first_time_run. korotagger migrate will only apply new migrations already and we probably want new migrations applied after updates
sorry for the slow response, i think there's just the one thing left to fix. it probably makes sense to leave the 100MB memory limit for korotagger. korotagger usually only uses around 12MB at most. |
No description provided.