Server Overview
| Component | Role | Port / Path | Status |
|---|---|---|---|
| Nginx | Reverse Proxy, TLS termination | 443 / 80 | Active |
| SYNTX Production API | Main orchestration & prompt workflow | /api/* → 8020 | systemd (running) |
Active Services (systemd)
| Service | Description | Working Directory | Port | Status |
|---|---|---|---|---|
syntx-api.service |
Main SYNTX Production API | /opt/syntx-workflow-api-get-prompts |
8020 | active (running) |
syntx-injector.service |
Field Resonance & Wrapper Injection API | /opt/syntx-injector-api |
8001 | active (running) |
syntx.service |
Local LLM Backend (Ollama / Uvicorn) | /var/www/syntx |
8000 | active (running) |
All SYNTX services are supervised via systemd with automatic restart.
External access is exclusively routed through Nginx.
Nginx Routing & Public Endpoints
| Public Path | Internal Target | Purpose |
|---|---|---|
/api/chat |
127.0.0.1:8001 |
Primary LLM interaction endpoint (Injector API) |
/resonanz/* |
127.0.0.1:8001/resonanz/ |
Field resonance diagnostics & system state |
/api/* |
49.13.3.21:8000 |
Legacy / LLM backend routing |
/monitoring/* |
127.0.0.1:8020 |
Queue & system health monitoring |
/strom/* |
127.0.0.1:8020 |
System flow & heartbeat endpoints |
/feld/* |
127.0.0.1:8020 |
Field analysis & diagnostics |
/docs/ |
/var/www/syntx-api-docs |
Static documentation (this page) |
/logs/ |
/opt/syntx-config/logs |
Protected system & training logs |
Nginx is the single public gateway.
No SYNTX service is directly exposed to the internet.
Routing rules are static, explicit and intentional.
Queue System & Data Flow
The SYNTX workflow uses a filesystem-based queue. All jobs move through clearly defined stages. The system is self-regulating and monitored continuously.
| Directory | Purpose | Current Size |
|---|---|---|
queue/incoming |
Newly generated jobs waiting for processing | ~104 KB |
queue/processing |
Jobs currently being processed | ~4 KB |
queue/processed |
Successfully completed jobs | ~7.2 MB |
queue/archive |
Archived historical jobs | ~3.6 MB |
queue/error |
Failed or invalid jobs | ~68 KB |
Jobs move strictly forward through the queue.
No job is overwritten.
Errors are isolated and never block the main flow.
Queue Health & Failure Handling
The queue currently operates in a low-pressure, stable state. There is no backlog, no stalled processing and no cascading failure behavior.
| Queue Segment | Current State | Operational Meaning |
|---|---|---|
| incoming | Contains pending response files | Normal producer output, system ready for processing |
| processing | Empty | No blocking jobs, consumers keep up in real time |
| error | Retry-only jobs (_retry1) | Controlled failure handling, no infinite retry loops |
Failures never block the system.
Each failed job is isolated, logged and retried explicitly.
No job is lost. No job is silently dropped.