Repository navigation
Quick Fix: Ensure Nginx Honors depends_on clause - #1346
happycodemonkey wants to merge 1 commit into
Conversation
…be up before trying to start itself
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1346 +/- ##
=======================================
Coverage 64.15% 64.15%
=======================================
Files 464 464
Lines 13853 13853
Branches 2767 2767
=======================================
Hits 8888 8888
Misses 4611 4611
Partials 354 354
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
wesleyboar
left a comment
There was a problem hiding this comment.
(I reviewed this, wondering if Core-CMS docker-compose could benefit.)
I think this change, as is, has no effect (Docker Docs suggest this change is equivalent to the "short syntax"), but that this long format might yet achieve your goal, because docs also suggest service_healthy is a different value that could help if you define a successful "healthcheck" for cms and django.
|
@wesleyboar thanks for taking a look and adding your feedback, this change does solve the issue I was having with my dev environment but I'm unclear why the short syntax doesn't work at all for me while the full one does, perhaps some weirdness with docker versions? I am curious if anyone else has had issues with this. I will look into defining the healthcheck as you suggested though, that seems like it will be more generally useful. |
Overview
No ticket for this one, I have noticed on my dev environment nginx will almost always fail to come up because it is not properly waiting on cms and django to be up. I have updated the depends_on clause as detailed in the docker documentation to tell it to wait until both services have started.
Related
No tickets involved
Changes
Updated depends_on to include service_started condition in the nginx block
Testing