Files
claudetools/.claude/memory/feedback_dashboard_beta_first.md
Mike Swanson 11d2b17b7d docs(gururmm): record dashboard beta-first channel + memory
- wiki/projects/gururmm.md: beta-first dashboard channels (rmm-beta) + wiring
- .claude/memory: feedback_dashboard_beta_first + index line
- bump guru-rmm submodule pointer to the beta-channel commit

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-02 20:14:52 -07:00

1.9 KiB

name, description, metadata
name description metadata
feedback_dashboard_beta_first GuruRMM dashboard has a beta-first deploy model — push auto-builds to rmm-beta, prod is explicit promote only; never hand-rsync prod
type
feedback

The GuruRMM dashboard deploys beta-first (stood up 2026-06-02 at Mike's request, partly to keep Howard's changes off prod until reviewed). Mirrors the agent beta/stable channel model.

  • betahttps://rmm-beta.azcomputerguru.com, web root /var/www/gururmm/dashboard-beta. Auto-builds on every push to main touching dashboard/ (/opt/gururmm/build-dashboard.sh, dispatched by the webhook alongside agent/server builds, change-gated on last-built-commit-dashboard). Shows a BETA banner.
  • prodhttps://rmm.azcomputerguru.com, web root /var/www/gururmm/dashboard. Updated ONLY via sudo /opt/gururmm/promote-dashboard.sh --confirm (dry-run by default; backs up prod, keeps last 10; --rollback restores).

Why: A preview channel lets dashboard changes soak before they hit the production RMM that ~55 agents and clients use; explicit promotion makes prod deploys deliberate and reversible.

How to apply: Never npm run build && rsync ... /var/www/gururmm/dashboard/ by hand — that's superseded and bypasses backup/soak. One artifact serves both channels (Vite bakes in the absolute prod API URL rmm-api.azcomputerguru.com, so beta uses shared prod data and is byte-identical to prod); beta is branded by an nginx-layer sub_filter banner, so promotion is a plain rsync. Serving: 2nd nginx vhost on .30 (deploy/nginx/rmm-beta.conf), Cloudflare rmm-beta A→72.194.62.10 proxied (mirrors rmm), Jupiter NPM host id=11 → .30:80 presenting cert id=10 (zone SSL mode is Full). Full wiring in deploy/build-pipeline/README.md (Dashboard channels). Related: feedback_gururmm_build_channel_default, feedback_gururmm_builds, reference_gitea_internal.