mirror of https://github.com/alexhopeoconnor/dnsmasq-webui.git synced 2026-10-03 22:12:00 +10:00

Files

T

alex 2e713f0e3c Hosts UX, effective names, JS interop, domain UI

- Hosts: delete confirmation modal, shift range select, keyboard shortcuts,
  effective-name suffix tooltips, conditional modern header actions
- Align EffectiveNames on rows with scoped domain= + pending preview;
  unified hosts API uses full DomainValues from config snapshot
- Harden Blazor JS interop (safe helpers, IAsyncDisposable, disposal order)
- Effective config: domain multi-value display/editor, parsers, tests
- Misc: docs/testdata/docker script updates

2026-04-05 14:46:17 +10:00

4.9 KiB

Raw Blame History

Agent instructions: dnsmasq-webui

Test harness (Docker)

The test harness runs the app and dnsmasq in Docker with DHCP clients so you can test the UI and effective config against real dnsmasq.

Script: scripts/prepare-test-mount.sh
Compose file: docker-compose.test.yml

Start the harness

From the repo root:

./scripts/prepare-test-mount.sh

This will:

Run docker compose down, then sync testdata/ → testdata-mount/ (preserving mount contents unless you pass --clear). Sync skips leases and zz-dnsmasq-webui.conf / zz-dnsmasq-webui.hosts so rebuilds keep DHCP leases and UI-written managed files.
Optionally remove managed *dnsmasq-webui*.conf / *dnsmasq-webui*.hosts in the mount only if you pass --reset-managed.
Resolve the requested dnsmasq version (latest by default) to a concrete value when building images.
Run docker compose -f docker-compose.test.yml up -d (add --build / --no-cache-build when you need a rebuild).

Quick restart (no image rebuild): ./scripts/prepare-test-mount.sh --no-build
Force a fresh image build: ./scripts/prepare-test-mount.sh --no-cache-build
Pin dnsmasq version: ./scripts/prepare-test-mount.sh --dnsmasq-version 2.91 --build
Use distro package: ./scripts/prepare-test-mount.sh --dnsmasq-version distro --build
Prepare mount only (no start): ./scripts/prepare-test-mount.sh --prepare-only
Then start manually with the version printed by the script: TESTDATA_MOUNT=./testdata-mount DNSMASQ_VERSION=<resolved-version> docker compose -f docker-compose.test.yml up -d [--build]
Preserve mount (e.g. keep leases and managed config): default; also use ./scripts/prepare-test-mount.sh --no-build for a quick up without rebuilding images.
Drop managed conf/hosts only (keep leases): ./scripts/prepare-test-mount.sh --reset-managed (often combined with --build).

App is at http://localhost:8080. Main config path in the container is /data/dnsmasq-test.conf; managed file is zz-dnsmasq-webui.conf in the same directory. The app service has a healthcheck (GET /healthz/ready); DHCP client services use depends_on: app: condition: service_healthy so they start only after the app (and dnsmasq) is ready.

Stop the harness

./scripts/prepare-test-mount.sh --stop

Runs docker compose -f docker-compose.test.yml down (stops and removes containers/networks). Does not change the mount directory.

Clean (stop + clear mount)

./scripts/prepare-test-mount.sh --tidy

Stops the harness and deletes the contents of testdata-mount/ so the next run starts from a clean sync of testdata/.

Custom paths

--source DIR — Source to sync from (default: testdata)
--mount DIR — Mount directory (default: testdata-mount). The script exports TESTDATA_MOUNT=./DIR when you use --mount, so compose uses it.
--dnsmasq-version V — Dnsmasq version for the harness image: latest (default), distro, or an exact upstream version like 2.91.
--reset-managed — After sync, delete *dnsmasq-webui*.conf and *dnsmasq-webui*.hosts under the mount so the app recreates them.
--no-cache-build — Force a fresh image build with docker compose build --pull --no-cache before start.

Example: sync from a custom dir and start:

./scripts/prepare-test-mount.sh --source myfixtures --mount mymount

Help

./scripts/prepare-test-mount.sh -h

Unit tests