Andrey Kizimenko
8c6bedf661
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** N/A — internal developer tooling (`tools/hangar`). ## Summary Fleet Hangar is the local dev-environment control panel (`tools/hangar`, Go + Wails). This PR expands it into a broader **local dev-services** toolkit for contributors/QA: - **Multi-server support** — run up to 3 independent local Fleet servers in parallel, each on its own git worktree, offset ports, and docker compose project (server switcher + server-scoped Server/Logs/Database/Git tabs). - **SCEP tab** — run local SCEP CA servers using the in-repo `server/mdm/scep/cmd/scepserver` (built once to a cached binary). Per-depot profiles, `ca -init`, concurrent start/stop with live logs, and one-click copy for the SCEP URL / challenge / thumbprint (parsed from `ca.pem`). - **MDM assets tab** — run `tools/mdm/assets export` from saved configs; results list each written file with copy-contents/path + size + timestamp, plus the `FLEET_MDM_APPLE_*` env block. - **TUF tab** — drive `tools/tuf/test/main.sh` from platform checkboxes. Hangar runs the file-server itself (`SKIP_SERVER=1`) so `fleetctl package` can reach the TUF URL during packaging; streams live build output; shows ngrok tunnel + TUF-server prerequisites; and offers kill-server + delete-assets. - **Supporting work** — DB backups in app-data + cross-server restore; ngrok live public-URL links + stale-tunnel heal; per-server open-in-browser; Settings → Troubleshoot cards to reap stray `scepserver`/TUF-server processes and delete `test_tuf`. Opening as a **draft for transparency**. All changes are confined to `tools/hangar/`; nothing touches the Fleet server, agent, or any shipped code. **Architecture:** each tab is an `internal/<feature>` package (pure, unit-tested logic) behind a thin `services/<feature>_service.go` Wails adapter, reached from the UI as `api.*`. Long-running processes go through the shared process engine; everything builds from / runs against the primary repo (Server 1). # Checklist for submitter If some of the following don't apply, delete the relevant line. - [ ] Changes file added for user-visible changes — N/A: `tools/hangar` is a developer tool and is not part of a Fleet release. - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented, JS inline code is prevented, and untrusted data interpolated into shell scripts/commands is validated against shell metacharacters. - External commands (`scepserver`, `go run ./tools/mdm/assets`, `bash main.sh`, the backup/restore `docker` invocation) are spawned with discrete argv slices via the process engine — no shell string interpolation — so user-supplied values (challenge, enroll secret, depot/dir paths) can't inject. Backup names are validated to `[A-Za-z0-9._-]`; server-id path segments are sanitized to `[A-Za-z0-9_-]` (no traversal); TUF asset deletion is scoped to `<repo>/test_tuf`. - [x] Timeouts are implemented and retries are limited to avoid infinite loops - Binary builds / one-shot commands run under bounded `context.WithTimeout`; the TUF-server readiness and ngrok local-API fetches use short HTTP timeouts; no unbounded loops or retries were added. - [ ] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI — N/A: no Fleet server API changes. ## Testing - [x] Added/updated automated tests - Go unit tests across the new packages: `settings` (SCEP profiles, TUF config, `migrate` incl. the empty-`servers` case), `scep` (depot/CA parsing, arg builders), `mdmassets` (export args, `wrote … in …` parsing, config persistence), `tuf` (env building, file-server args, asset delete), and `troubleshoot` (live-PID filtering) — plus the existing backups logic. - `tsc --noEmit` clean and `task build` green. - [ ] Where appropriate, automated tests simulate multiple hosts and test for host isolation — N/A. - [x] QA'd all new/changed functionality manually (ongoing local testing of all three tabs). ## Database migrations N/A — no database migrations. ## New Fleet configuration settings N/A — no Fleet server configuration settings (Hangar stores its own settings in app-data). ## fleetd/orbit/Fleet Desktop N/A — no fleetd/orbit/Fleet Desktop changes. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Multi-server support (up to three) with server switcher, server-scoped health/logs, and server-scoped Docker Compose controls. * New **Servers** settings section plus per-server configuration (including ports/compose project) and server-aware start/stop/quit flows. * New **SCEP**, **MDM Assets**, and **TUF** tabs for managing profiles/assets and discovering ngrok URLs. * Git worktree listing/creation/removal. * Centralized, server-scoped database backup management. * **Bug Fixes** * Improved process discovery to skip dead or racing entries and avoid duplicate docker-compose-up display. * Self-healing pruning of stale ngrok tunnel selections. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
49 lines
1.3 KiB
YAML
49 lines
1.3 KiB
YAML
version: '3'
|
|
|
|
vars:
|
|
# APP_NAME is the executable / binary name (hyphenated: reused for the
|
|
# `-server` binary and Docker image tags, where spaces would break things).
|
|
APP_NAME: "fleet-hangar"
|
|
# PRODUCT_NAME is the user-facing `.app` bundle name shown in Finder/Launchpad.
|
|
PRODUCT_NAME: "Fleet Hangar"
|
|
BIN_DIR: "bin"
|
|
PACKAGE_MANAGER: '{{.PACKAGE_MANAGER | default "npm"}}'
|
|
VITE_PORT: '{{.WAILS_VITE_PORT | default 9245}}'
|
|
|
|
includes:
|
|
common: ./build/Taskfile.yml
|
|
darwin: ./build/darwin/Taskfile.yml
|
|
|
|
tasks:
|
|
build:
|
|
summary: Builds the application
|
|
cmds:
|
|
- task: "{{OS}}:build"
|
|
|
|
package:
|
|
summary: Packages a production build of the application
|
|
cmds:
|
|
- task: "{{OS}}:package"
|
|
|
|
dist:
|
|
summary: Zips the already-built .app into a single shareable archive (bin/Fleet Hangar.zip)
|
|
cmds:
|
|
- task: "{{OS}}:dist"
|
|
|
|
pkg:
|
|
summary: Wraps the already-built .app into a Fleet-installable .pkg (bin/Fleet Hangar.pkg)
|
|
cmds:
|
|
- task: "{{OS}}:pkg"
|
|
|
|
run:
|
|
summary: Runs the application
|
|
cmds:
|
|
- task: "{{OS}}:run"
|
|
|
|
dev:
|
|
summary: Runs the application in development mode (Ctrl+C also stops the Vite dev server)
|
|
cmds:
|
|
# Wrapper script (real bash) traps Ctrl+C and frees the Vite port, which
|
|
# wails3 dev otherwise orphans. See scripts/dev.sh.
|
|
- bash scripts/dev.sh {{.VITE_PORT}}
|