Healthchecks for each service #1
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#1
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Required because swarm uses this to do zero downtime deployments.
Must also be accompanied by the
order: start-first
configuration.See the following for a working example:
I tried adding one to Mediawiki and I saw the requests in the log, but I wasn't able to force the check to fail to make sure it's working -- commenting out the last line of
/docker-entrypoint2.sh
(entrypoint.sh.tmpl
in the repo) didn't help.Any tips on testing a fail?
Hmmm, I think I was just running a fresh image in one terminal and then in the other running the healthcheck command via
docker exec
and checking it failed/worked. To get the initial start-up time, you need to nuke the volumes so that it takes a while for the container to come up properly. Make sure you aredocker context use default
for that :)Remaining ones are the following:
I guess I'll leave this ticket open to document that when adding a new app, you should at least try to see about the healthcheck. It isn't always easy to do. A lottttt of our apps have them now though 💯
Yep I've been tracking them on the app status page too 👌
Covered by the README standard 🚀