Healthchecks for each service #1

Closed
opened 2020-06-25 11:01:44 +00:00 by decentral1se · 5 comments
Owner

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:

https://git.autonomic.zone/autonomic-cooperative/git.autonomic.zone/src/branch/master/compose.yml

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: > https://git.autonomic.zone/autonomic-cooperative/git.autonomic.zone/src/branch/master/compose.yml
Owner

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?

[I tried adding one to Mediawiki](https://git.autonomic.zone/compose-stacks/mediawiki/commit/26ca41aa91ba0ac637250f6523a8a6f50917b310) 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?
Author
Owner

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 are docker context use default for that :)

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 are `docker context use default` for that :)
3wordchant added the
enhancement
label 2020-09-24 23:15:15 +00:00
Author
Owner

Remaining ones are the following:

➜  gardening (main) ✔ grep -riL "healthcheck" clones | grep -i compose.yml
clones/mediawiki/compose.yml
clones/strapi/compose.yml
clones/matrix-synapse/compose.yml
clones/foodsoft/compose.yml
clones/invoiceninja/compose.yml
clones/portainer/compose.yml

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 💯

Remaining ones are the following: ``` ➜ gardening (main) ✔ grep -riL "healthcheck" clones | grep -i compose.yml clones/mediawiki/compose.yml clones/strapi/compose.yml clones/matrix-synapse/compose.yml clones/foodsoft/compose.yml clones/invoiceninja/compose.yml clones/portainer/compose.yml ``` 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 💯
decentral1se added
documentation
and removed
enhancement
labels 2020-10-27 07:56:45 +00:00
decentral1se added this to the Public mini-launch milestone 2020-10-27 08:05:22 +00:00
Owner

Yep I've been tracking them on the app status page too 👌

Yep I've been tracking them on the [app status page](https://codimd.autonomic.zone/49--AK0GQDWoxMq6-9ngTQ?edit) too 👌
decentral1se added this to the (deleted) project 2020-12-27 11:49:30 +00:00
decentral1se removed this from the Public mini-launch milestone 2021-03-02 09:15:34 +00:00
decentral1se added this to the (deleted) milestone 2021-03-02 12:26:24 +00:00
Author
Owner

Covered by the README standard 🚀

Covered by the README standard 🚀
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#1
No description provided.