M41: harden trust boundaries and delivery
This commit is contained in:
+6
-6
@@ -71,8 +71,8 @@ On startup the API creates the first active Operations Manager only when no user
|
||||
email exists. The sign-in page then accepts email/password instead of exposing demo roles;
|
||||
demo reset, the guided tour and the synthetic-data badge are hidden.
|
||||
|
||||
Use a long unique `APP_SECRET`, set `SESSION_COOKIE_SECURE=true` once the public endpoint
|
||||
uses HTTPS, and keep `INITIAL_ADMIN_PASSWORD` out of Git and logs. Existing sessions are
|
||||
Use a long unique `APP_SECRET`; production requires an HTTPS public endpoint and
|
||||
`SESSION_COOKIE_SECURE=true`. Keep `INITIAL_ADMIN_PASSWORD` out of Git and logs. Existing sessions are
|
||||
revalidated against the current user record on every request, so deactivating an account
|
||||
invalidates its next request.
|
||||
|
||||
@@ -168,17 +168,17 @@ deliberately published with a real service token.
|
||||
|
||||
### Existing shared n8n on the Unraid review server
|
||||
|
||||
The Unraid deployment uses the existing n8n at `http://192.168.10.150:5678`; it does not
|
||||
The Unraid deployment uses the existing n8n at `https://n8n.itworx.tech`; it does not
|
||||
start MobilityOps's bundled n8n service. `compose.unraid.yaml` places that fallback behind
|
||||
the opt-in `bundled-n8n` profile. Configure the API target and publish the workflow with:
|
||||
|
||||
```bash
|
||||
sed -i \
|
||||
's|^N8N_WEBHOOK_URL=.*|N8N_WEBHOOK_URL=http://192.168.10.150:5678/webhook/mobilityops-return|' \
|
||||
's|^N8N_WEBHOOK_URL=.*|N8N_WEBHOOK_URL=https://n8n.itworx.tech/webhook/mobilityops-return|' \
|
||||
.env
|
||||
./deploy/unraid/setup-existing-n8n.sh \
|
||||
n8n \
|
||||
http://192.168.10.150:1236/api/v1/integrations/n8n/return-callback
|
||||
https://fleetops.itworx.tech/api/v1/integrations/n8n/return-callback
|
||||
docker compose -p mobilityops -f compose.yaml -f compose.unraid.yaml up -d db api web
|
||||
```
|
||||
|
||||
@@ -215,7 +215,7 @@ Publish the scheduled quality-scan workflow the same way:
|
||||
```bash
|
||||
./deploy/unraid/setup-scheduled-scan.sh \
|
||||
n8n \
|
||||
http://192.168.10.150:1236/api/v1/integrations/n8n/scheduled-scan
|
||||
https://fleetops.itworx.tech/api/v1/integrations/n8n/scheduled-scan
|
||||
```
|
||||
|
||||
## Required operational checks
|
||||
|
||||
Reference in New Issue
Block a user