-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: create scheduler (resolves #646) #687
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #687 +/- ##
============================================
- Coverage 92.93% 92.33% -0.60%
- Complexity 1111 1116 +5
============================================
Files 196 198 +2
Lines 3240 3261 +21
============================================
Hits 3011 3011
- Misses 229 250 +21
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
A couple of suggestions/questions. Also wondering where the schedule is run on the staging environment?
Co-authored-by: Ned Zimmerman <ned@bight.dev>
Currently we aren't running a cron to hit scheduler in staging. We would need to open an issue and have Jure implement one into the Kube. |
Reverted workflows, the changes seemed to cause testing failures. |
Added new command
deploy:initial
which is where we will put everything that we need to run at boot time. Then we only add this command into entrypoint script and make all changes within this command.Made update to entrypoint script.
Added new command
db:refresh
which chainsmigrate:fresh
&db:seed
commands.Added schedule to run command
db:refresh
to run nightly on environments tagged with staging or local.