Runtime
Node API
Express-based backend service responsible for exposing structured infrastructure and deployment data to the lab frontend.
Benjibusco Lab / API
Frontend interface for exploring backend services, endpoint structure, deployment metadata, infrastructure metrics, and the systems powering the lab ecosystem.
Backend Service
Raw backend service endpoint that currently exposes live status, deployment, uptime, and infrastructure data for the lab ecosystem.
Live Health
Dedicated status page for checking whether the lab ecosystem, API service, deployments, and server resources are healthy right now.
Runtime
Express-based backend service responsible for exposing structured infrastructure and deployment data to the lab frontend.
Reverse Proxy
Apache routes public API traffic from the backend subdomain to the internal Node service running on the VPS.
Process Manager
PM2 keeps the API service online, managed, and ready for future monitoring, restart, and process visibility workflows.
Resource
Tracks current processor usage for infrastructure visibility and future observability dashboards.
Resource
Reports server memory usage to help monitor resource pressure across the lab environment.
Resource
Provides filesystem usage data for deployment, storage, and long-term server maintenance awareness.
System
Displays how long the VPS environment has been running since the last restart.
GET
Returns structured status data for service health, deployment metadata, uptime, CPU usage, memory usage, disk usage, and timestamp information.
Future
Future API routes can support deployment history, logs, service checks, project data, docs metadata, and internal lab tooling.
CI/CD
Deployment metadata connects the frontend lab environment with GitHub Actions, commit tracking, branch data, and production release visibility.
Repository
The API can expose branch and commit information so the lab dashboard can show what version is currently deployed.
Automation
GitHub Actions updates deployment data during production deploys, giving the lab a stronger foundation for release tracking.
Separation
The lab API page explains and visualizes backend services without replacing the raw backend subdomain or the dedicated status dashboard.
Backend
The backend API lives on its own subdomain and acts as the service layer for structured data, metrics, and future integrations.
Direction
This page can evolve into a frontend/backend integration dashboard for endpoint documentation, monitoring, deployment history, and service visibility.