officecom/oc-sentinel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 21 Wiki Activity

Track internal Postgres target in release process
Some checks failed
OfficeCom Sentinel Client / build-client (push) Has been cancelled
Details

Browse Source
This commit is contained in:
OfficeCom Codex
2026-07-17 01:12:38 +02:00
parent fde24f2616
commit 05029c9fb2
5 changed files with 53 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/ocsentinel-architecture.md
View File

@@ -19,6 +19,15 @@ The repository now keeps only the client-side architecture:
- optional n8n upload
- packaged ZIP release flow for NinjaOne deployment
The client must not depend on a PostgreSQL IP or hostname. PostgreSQL stays a server-side concern behind the ingest or n8n layer.
## PostgreSQL Handling
- PostgreSQL is not contacted directly by endpoint clients.
- The PostgreSQL host or IP should be tracked in the repository only as internal deployment metadata.
- Review that internal target on every release before publishing.
- Keep the actual production value in a private operational copy if it should not be visible in the public repository.
## Removed Model
The following older pieces are intentionally no longer part of the repo: