tiennm99 b1911c0538 ci: make alloy smoke-test robust to runtime errors
Previous step failed in CI because the bare alloy container had no
/var/log/journal, no docker.sock, etc., so loki.source.journal +
discovery.docker exited the process — and --rm wiped the container
before logs could be inspected.

Now: drop --rm, mount the same host paths the prod compose uses, plus
an empty /var/log/journal stand-in. Capture logs unconditionally and
fail only on config-level patterns ('unknown component',
'undefined reference', 'syntax error', etc.). Runtime/component
failures against dummy endpoints are tolerated.
2026-04-25 19:12:05 +07:00
2025-04-07 12:44:18 +07:00
2025-03-24 21:18:44 +07:00
2025-03-07 00:42:01 +07:00
2025-03-25 21:58:42 +07:00
2023-12-23 08:15:16 +07:00
2024-05-03 16:38:43 +07:00
S
Description
Docker Compose files for the services I self-host — Gitea mirror, Couchbase, code-server, Grafana Alloy, coding-agent UIs and more — deployed through Coolify and Dokploy
Apache-2.0
645 KiB
0 Stars 1 Watchers 0 Forks
Languages
Shell 69.7%
Dockerfile 30.3%