web-ng-docker-loop
Skill932 starsChanged 12 days agoApache-2.0View on GitHub
Run ServiceRadar `elixir/web-ng` locally against the Docker Compose CNPG database with copied mTLS certs and Docker secrets, then verify dashboard UI changes with Playwright. Use when iterating on web-ng, dashboard package, custom React dashboard, customer WiFi map, SRQL topbar, or browser screenshot behavior without rebuilding the web-ng release image.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- openspec/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- daisyuiSkill
- demo-cnpg-local-web-ngSkill
- demo-local-rolloutSkill
- demo-web-ng-fastpathSkill
- fieldsurvey-local-web-ngSkill
- playwright-cliSkill
- release-cut-and-demo-rollSkill
- serviceradar-bazel-guardrailsSkill
- serviceradar-build-testSkill
- serviceradar-dependenciesSkill
- serviceradar-elixirSkill
- serviceradar-openspecSkill
- serviceradar-operationsSkill
- srql-fixtures-db-testsSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill for fast local UI iteration when Docker Compose is already running the ServiceRadar mTLS stack.
- Distinctive: line 25
If the app database password in Docker secrets does not match the local CNPG role, rerun once with:
- Distinctive: line 35
After rebuilding a dashboard package, import it into the Docker-backed database without rebuilding web-ng:
- Very specific: line 48
Use $playwright-cli for interactive inspection and screenshots:
- Very specific: line 56
If authentication is required, obtain the admin password from docker compose logs config-updater without writing it into committed files.
- Very specific: line 60
Keep generated certs and screenshots under tmp/.
- Very specific: line 61
Stop stale local Phoenix servers before starting a new one: pkill -f 'mix phx.server'.
- Very specific: line 62
Use the Docker route (https://192.168.2.134/...) only for final parity after local checks pass.
- Very specific: line 63
Run npm run build:js && npm run build:css in elixir/web-ng/assets after JS/CSS changes before browser checks.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Web-NG Docker Loop
Use this skill for fast local UI iteration when Docker Compose is already running the ServiceRadar mTLS stack. Prefer this loop over Bazel/release-image rebuilds until the final Docker parity check.
Quick Start
From the ServiceRadar repo root:
.agents/skills/web-ng-docker-loop/scripts/start-local-web-ng.shThe script:
- copies
root.pem,db-client.pem, anddb-client-key.pemfrom the Docker web-ng cert mount intotmp/web-ng-docker-loop/certs/ - reads the CNPG app password from the running Docker secret without printing it
- validates the local host connection to
localhost:5455 - syncs Docker filesystem plugin/dashboard package blobs into
tmp/web-ng-docker-loop/plugin-packages/ - starts
mix phx.serverinelixir/web-ngonhttp://localhost:4000
If the app database password in Docker secrets does not match the local CNPG role, rerun once with:
.agents/skills/web-ng-docker-loop/scripts/start-local-web-ng.sh --repair-app-passwordThat repair path is only for the local Docker Compose stack; it uses the Docker superuser secret to reset the Docker serviceradar role to the Docker app secret.
Dashboard Package Import
After rebuilding a dashboard package, import it into the Docker-backed database without rebuilding web-ng:
.agents/skills/web-ng-docker-loop/scripts/import-dashboard-package.sh \
/home/mfreeman/src/example-dashboard/dist/manifest.json \
/home/mfreeman/src/example-dashboard/dist/renderer.jsThis imports and enables the package through the running Docker web-ng release RPC, then prints the enabled content hash. Restart the local loop, or rerun it with the default plugin-storage sync enabled, after importing a new dashboard renderer.
Browser Checks
Use $playwright-cli for interactive inspection and screenshots:
playwright-cli open http://localhost:4000/dashboards/wifi-network-map
playwright-cli snapshot
playwright-cli screenshot --filename=tmp/wifi-map-local.pngIf authentication is required, obtain the admin password from docker compose logs config-updater without writing it into committed files.
Notes
- Keep generated certs and screenshots under
tmp/; do not commit them. - Stop stale local Phoenix servers before starting a new one:
pkill -f 'mix phx.server'. - Use the Docker route (
https://192.168.2.134/...) only for final parity after local checks pass. - Run
npm run build:js && npm run build:cssinelixir/web-ng/assetsafter JS/CSS changes before browser checks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.