🛑Periphery... yeah, I can't get it working — the passkey header and everything just don't seem to play nice.
Originally created by @Norrodar on GitHub (May 21, 2025).
I like to monitor all my containers for their health status — mostly just to satisfy my inner monk.

✅ **Postgres** is straightforward:
```
healthcheck:
test:
- CMD-SHELL
- pg_isready -U ${KOMODO_DB_USERNAME} -d ${KOMODO_DATABASE_DB_NAME}
interval: 10s
timeout: 5s
retries: 5
start_period: 30s
```
✅ **FerretDB** has its own internal healthcheck, which communicates with Docker (e.g., for Dockge).
⚠️ For **Core**, I built the absolute basics:
```
healthcheck:
test:
- CMD
- curl
- -f
- http://localhost:9120
interval: 30s
timeout: 10s
retries: 5
```
🛑 **Periphery**... yeah, I can't get it working — the passkey header and everything just don't seem to play nice.
@djakupovic commented on GitHub (Jul 1, 2025):
healthcheck:
test: ["CMD-SHELL", "wget -q --spider http://127.0.0.1:8121 || exit 1"]
interval: 10s
retries: 3
start_period: 10s
This works for me as a workaround
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Norrodar on GitHub (May 21, 2025).
I like to monitor all my containers for their health status — mostly just to satisfy my inner monk.

✅ Postgres is straightforward:
✅ FerretDB has its own internal healthcheck, which communicates with Docker (e.g., for Dockge).
⚠️ For Core, I built the absolute basics:
🛑 Periphery... yeah, I can't get it working — the passkey header and everything just don't seem to play nice.
@djakupovic commented on GitHub (Jul 1, 2025):
healthcheck:
test: ["CMD-SHELL", "wget -q --spider http://127.0.0.1:8121 || exit 1"]
interval: 10s
retries: 3
start_period: 10s
This works for me as a workaround
@chiragkrishna commented on GitHub (Oct 4, 2025):
came searching for this, checking health is way complicated
Would give output