threadmill-dashboard-ui
Static operations console for Threadmill.
The UI is a Vite React/TypeScript app using Tailwind CSS, shadcn-style local
components, lucide icons, and TanStack Table. It is designed to be served at
/threadmill with the JSON API available from the same origin at
/threadmill/api/**, so Spring Security sessions and CSRF tokens work without
CORS or separate browser tokens.
The Gradle jar packages the built app under
META-INF/resources/threadmill/. Framework adapters can serve that same jar;
the Spring adapter mounts it automatically when present.
The Spring adapter emits /threadmill/config.js from
threadmill.dashboard.api.base-path, so a mounted console follows a custom API
path without host-page changes. The asset jar includes an empty fallback
config.js, so development and non-Spring mounts keep the default API path
without a missing-script error. Other adapters can override that file or
provide the same runtime value before the app loads:
<script> window.__THREADMILL_DASHBOARD_CONFIG__ = { apiBasePath: "/admin/threadmill/api" };</script>npm installnpm run testnpm run buildGradle also wires the static build into :threadmill-dashboard-ui:check.
Browser smoke tests
Section titled “Browser smoke tests”The Playwright suite starts a real Spring Boot dashboard with the packaged UI, HTTP Basic authentication, cookie CSRF, seeded operator data, and a non-default API base path. Install Chromium once, then run the Gradle-owned suite:
./gradlew :threadmill-dashboard-ui:npmInstallcd threadmill-dashboard-ui && npx playwright install chromium && cd .../gradlew :threadmill-dashboard-spring:browserTestFailures retain screenshots, video, traces, and an HTML report under
threadmill-dashboard-ui/build/. CI uploads those files as the
dashboard-browser-failure artifact.
Layout
Section titled “Layout”The console is intentionally dense: state filters, a 50-job paged table with previous/next controls, queue controls, recurring task controls, node heartbeats, and a job detail drawer are all visible without a landing page. Permission-gated actions are hidden or disabled in the UI, but the API remains authoritative.