Benjibusco Lab / API

API

Frontend interface for exploring backend services, endpoint structure, deployment metadata, infrastructure metrics, and the systems powering the lab ecosystem.

Service Overview

Runtime

Node API

Express-based backend service responsible for exposing structured infrastructure and deployment data to the lab frontend.

Reverse Proxy

Apache Proxy

Apache routes public API traffic from the backend subdomain to the internal Node service running on the VPS.

Process Manager

PM2

PM2 keeps the API service online, managed, and ready for future monitoring, restart, and process visibility workflows.

Infrastructure Metrics

Resource

CPU Usage

Tracks current processor usage for infrastructure visibility and future observability dashboards.

Resource

Memory Usage

Reports server memory usage to help monitor resource pressure across the lab environment.

Resource

Disk Usage

Provides filesystem usage data for deployment, storage, and long-term server maintenance awareness.

System

Uptime

Displays how long the VPS environment has been running since the last restart.

Endpoint Reference

GET

/status

Returns structured status data for service health, deployment metadata, uptime, CPU usage, memory usage, disk usage, and timestamp information.

Future

Additional Endpoints

Future API routes can support deployment history, logs, service checks, project data, docs metadata, and internal lab tooling.

Deployment Information

CI/CD

Latest Deployment

Deployment metadata connects the frontend lab environment with GitHub Actions, commit tracking, branch data, and production release visibility.

Repository

Branch & Commit

The API can expose branch and commit information so the lab dashboard can show what version is currently deployed.

Automation

Deployment Pipeline

GitHub Actions updates deployment data during production deploys, giving the lab a stronger foundation for release tracking.

Architecture Notes

Separation

Frontend API Interface

The lab API page explains and visualizes backend services without replacing the raw backend subdomain or the dedicated status dashboard.

Backend

Service Layer

The backend API lives on its own subdomain and acts as the service layer for structured data, metrics, and future integrations.

Direction

Observability Platform

This page can evolve into a frontend/backend integration dashboard for endpoint documentation, monitoring, deployment history, and service visibility.