DUMB services¶
The backend API and dashboard provide the management interface for the stack. They start with the container when enabled; the default configuration enables both.
At a glance¶
The frontend is where you work; the API coordinates the managed applications behind it.
flowchart TD
A["Your browser"] --> B["DUMB Frontend"]
B --> C["DUMB API"]
C --> D["Managed services"]
D --> E["Health, logs and task results"]
E --> B
DUMB service index¶
| Service | Default port | Purpose |
|---|---|---|
| DUMB API | 8000 |
Configuration, service control, logs, health, and background-job APIs |
| DUMB Frontend | 3005 |
Onboarding, dashboard, service pages, and settings |
The dashboard's server proxies browser requests to the API. In the maintained Docker setup, publish the frontend port; the backend can stay on loopback inside the container.
How they work¶
The backend coordinates managed service processes and shared state. The dashboard reads that state and sends requested actions to the API. Disabling the dashboard removes browser access but does not turn the backend into a different service manager. Disabling the API makes dashboard controls unavailable.
If the dashboard does not load¶
- Confirm the DUMB container is running and the frontend port is published.
- Inspect the DUMB Frontend and DUMB API startup logs.
- If the page opens but actions fail, check API connectivity and your authentication session.
- Use the ports saved in your running configuration if you changed the defaults.
See networking and ports, API reference, and dashboard guide.