remco/EpicNext-Cms
1
1 Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix(security): LAPI-only engine boot, import via stdin, correct compose service
Gitea Actions Runner Test / test-job (push) Successful in 1s
Details
CI / check (push) Successful in 29s
Details
CI / tests-integration (push) Successful in 1m46s
Details
CI / tests-unit (push) Successful in 1m59s
Details
CI / tests-ui (push) Successful in 2m53s
Details
CI / preflight (push) Skipped
Details
CI / deploy (push) Failing after 1m54s
Details

Browse Source
This commit is contained in:
openhands committed 2026-09-24 18:59:13 +02:00
1 parent 9562a75378
commit 7392b843ad
5 files changed
+24 -14
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

scripts/crowdsec-setup.sh
+1 -1
View File
@@ -147,7 +147,7 @@ while ! health_probe "http://127.0.0.1:$port/health"; do
sleep 2
done
printf 'CrowdSec engine running on 127.0.0.1:%s (container %s), reading %s/access.log.\n' "$port" "$CONTAINER_NAME" "$log_dir"
printf 'CrowdSec engine running in LAPI-only mode on 127.0.0.1:%s (container %s).\n' "$port" "$CONTAINER_NAME"
compose_cmd exec -T crowdsec cscli bouncers list >/dev/null 2>&1 \
&& printf 'Bouncer "cms" was registered against the local LAPI.\n' \
|| printf 'Warning: could not list bouncers. Diagnose with: docker compose exec -T %s cscli bouncers list\n' "$CONTAINER_NAME"