docs(devops): note restart and valkey write controls
This commit is contained in:
parent
4b9ae37ead
commit
3d0183b8c6
@ -17,6 +17,7 @@ The VM moved forward after the original snapshot:
|
||||
- `admin-web` and `tracker-web` are healthy again
|
||||
- `extraction-service` product rate limiting now uses Valkey-backed shared counters
|
||||
- the admin ops page now includes VM inventory and Valkey inspection panels
|
||||
- the admin ops page now includes allowlisted container restart actions and guarded Valkey delete actions
|
||||
- live verification confirmed a request for `productId=valkey-check-2` created the key `extraction:product-rate-limit:29582406:valkey-check-2` in Valkey with value `1`
|
||||
|
||||
### What is working
|
||||
|
||||
@ -207,9 +207,16 @@ The internal admin dashboard at `http://<vm-ip>:3001/ops` now exposes:
|
||||
- Mission Control health for the internal stack
|
||||
- a VM inventory view of Docker-managed services and host tooling
|
||||
- a read-only Valkey inspector for key pattern scans, TTLs, and small previews
|
||||
- restart buttons for allowlisted internal containers
|
||||
- guarded Valkey delete actions for exact keys and concrete prefix patterns
|
||||
|
||||
These views are protected by the admin dashboard auth layer.
|
||||
|
||||
Note:
|
||||
|
||||
- restart actions require the Docker socket to be mounted into `admin-web`
|
||||
- the current implementation mounts `/var/run/docker.sock` into the admin container, so this route should remain internal-only and admin-only
|
||||
|
||||
## Environment Variables
|
||||
|
||||
All optional — defaults work for most setups:
|
||||
|
||||
Loading…
Reference in New Issue
Block a user