clusev

Commit Graph

Author	SHA1	Message	Date
boban	e26921f33a	feat(ui): uniform bordered button kit; retire ghost variants Every x-btn variant now carries a persistent border + background. Replace the borderless `ghost`/`ghost-danger` (the latter only reddened on hover) with the bordered `secondary` and a new `danger-soft` (red-tinted border+bg, always). Migrate all 10 usages across servers/settings/files. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-14 10:18:47 +02:00
boban	221e49f24a	fix(hardening): detect fail2ban/ufw as installed via binary or active service The hardening checklist read "installed" from the package manager alone (dpkg `^ii` / rpm `-q`), so it disagreed with the live fail2ban/firewall panels, which use `command -v` + `systemctl is-active`. On a host where the component is genuinely present but not recorded as an apt `^ii` package — installed from source, or left in dpkg `rc` (config-only) state — the checklist showed `nicht installiert` while the panel reported it active with real bans (the reported contradiction). The installed probe now ORs three conditions: the package-manager test, the client binary on PATH, and the service already running. Since a component can never be active without being installed, this only removes FALSE negatives — it can never produce a false positive. Detection is now consistent with Fail2banService::status and FirewallTool. Applies to both fail2ban and the firewall (ufw/firewalld). Adds HardeningServiceTest covering the Debian/apt source-install fallback: the emitted probe gains `command -v fail2ban-client` and `dpkg -l ufw`, and an active component reads as featureOn. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-14 09:22:28 +02:00
boban	53f7309c0b	feat: scaffold — Dockerized Laravel 13 + Livewire 3 + Tailwind 4 + Reverb Working dev stack on :80 (Freigabe step 5: app boots, page renders, Vite HMR runs): - Multi-stage Dockerfile (php8.3-fpm + nginx + supervisor + node). Dev runs php-fpm + nginx + vite in ONE app container; prod target bakes vendor + assets. - docker-compose.yml (dev, bind-mount) + docker-compose.prod.yml (GHCR image). Env-driven ports/UID (APP_PORT, VITE_PORT, REVERB_HOST_PORT, DB_PORT, HOST_UID/HOST_GID) — nothing hardcoded. MariaDB only on 127.0.0.1:3306. - Laravel 13, Livewire 3.8 (class-based, no Volt), wire-elements/modal 2, phpseclib 3, laravel/reverb 1. composer platform pinned to php 8.3. - Tailwind v4 @theme tokens ("Tactical Terminal") in app.css; Vite remote HMR (host 0.0.0.0, hmr.host 10.10.90.136). - Dashboard as a full-page Livewire route (/) in layouts/app; §5 folder skeleton. - Docs: rules.md R1-R11 (incl. R11 UUID-in-URLs) + CLAUDE.md updated for Laravel 13, clusev/ root, port 80, vite-in-app, env-driven config. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-12 00:31:50 +02:00

Author

SHA1

Message

Date

boban

e26921f33a

feat(ui): uniform bordered button kit; retire ghost variants

Every x-btn variant now carries a persistent border + background. Replace the
borderless `ghost`/`ghost-danger` (the latter only reddened on hover) with the
bordered `secondary` and a new `danger-soft` (red-tinted border+bg, always).
Migrate all 10 usages across servers/settings/files.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-14 10:18:47 +02:00

boban

221e49f24a

fix(hardening): detect fail2ban/ufw as installed via binary or active service

The hardening checklist read "installed" from the package manager alone
(dpkg `^ii` / rpm `-q`), so it disagreed with the live fail2ban/firewall
panels, which use `command -v` + `systemctl is-active`. On a host where the
component is genuinely present but not recorded as an apt `^ii` package —
installed from source, or left in dpkg `rc` (config-only) state — the
checklist showed `nicht installiert` while the panel reported it active with
real bans (the reported contradiction).

The installed probe now ORs three conditions: the package-manager test, the
client binary on PATH, and the service already running. Since a component can
never be active without being installed, this only removes FALSE negatives —
it can never produce a false positive. Detection is now consistent with
Fail2banService::status and FirewallTool. Applies to both fail2ban and the
firewall (ufw/firewalld).

Adds HardeningServiceTest covering the Debian/apt source-install fallback:
the emitted probe gains `command -v fail2ban-client` and `dpkg -l ufw`, and an
active component reads as featureOn.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-14 09:22:28 +02:00

boban

53f7309c0b

feat: scaffold — Dockerized Laravel 13 + Livewire 3 + Tailwind 4 + Reverb

Working dev stack on :80 (Freigabe step 5: app boots, page renders, Vite HMR runs):
- Multi-stage Dockerfile (php8.3-fpm + nginx + supervisor + node). Dev runs
  php-fpm + nginx + vite in ONE app container; prod target bakes vendor + assets.
- docker-compose.yml (dev, bind-mount) + docker-compose.prod.yml (GHCR image).
  Env-driven ports/UID (APP_PORT, VITE_PORT, REVERB_HOST_PORT, DB_PORT,
  HOST_UID/HOST_GID) — nothing hardcoded. MariaDB only on 127.0.0.1:3306.
- Laravel 13, Livewire 3.8 (class-based, no Volt), wire-elements/modal 2,
  phpseclib 3, laravel/reverb 1. composer platform pinned to php 8.3.
- Tailwind v4 @theme tokens ("Tactical Terminal") in app.css; Vite remote HMR
  (host 0.0.0.0, hmr.host 10.10.90.136).
- Dashboard as a full-page Livewire route (/) in layouts/app; §5 folder skeleton.
- Docs: rules.md R1-R11 (incl. R11 UUID-in-URLs) + CLAUDE.md updated for
  Laravel 13, clusev/ root, port 80, vite-in-app, env-driven config.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-12 00:31:50 +02:00

3 Commits (e26921f33a85b1fa5f997158c3564588b95adcea)