Guides on Dev Knowledgebase

Workspace Guidelines

Sun, 31 May 2026 00:00:00 +0000

Repository Guidelines #

1. Workspace & Server Overview #

Development Environment: Running on a remote Debian 12 server (IP: 173.212.213.72, hostname: 0rk.de). The server is equipped with a high-performance multi-core CPU and significant memory, but operates WITHOUT GPU acceleration.
Workspace Architecture: The workspace at /home/dev/ contains multiple independent, fully realized systems rather than a single monorepo. It serves as a unified workspace for audio workstations, Music Information Retrieval (MIR) visualizers, static web hydration frameworks, and various active projects.
Target Guidelines Purpose: This document acts as a master map for AI agents and human developers operating inside /home/dev/ to understand the architecture, run configurations, coding standards, and testing protocols of all active sub-projects.

2. Projects & Architecture #

The workspace is organized into several distinct active domains:

MixBox Guidelines

Sun, 31 May 2026 00:00:00 +0000

Repository Guidelines #

1. Workspace & Server Overview #

Development Environment: Running on a remote Debian 12 server (IP: 173.212.213.72, hostname: 0rk.de). The server is equipped with a high-performance multi-core CPU and significant memory, but operates WITHOUT GPU acceleration.
Workspace Architecture: The workspace at /home/dev/ contains multiple independent, fully realized systems rather than a single monorepo. It serves as a unified workspace for audio workstations, Music Information Retrieval (MIR) visualizers, static web hydration frameworks, and various active projects.
Target Guidelines Purpose: This document acts as a master map for AI agents and human developers operating inside /home/dev/ to understand the architecture, run configurations, coding standards, and testing protocols of all active sub-projects.

2. Projects & Architecture #

The workspace is organized into several distinct active domains:

OMP Dashboard & Telemetry Blueprint

Wed, 10 Jun 2026 00:00:00 +0000

OMP Dashboard & Telemetry Blueprint #

This blueprint outlines the deployment architecture for the OMP Dashboard and OMP Telemetry (Stats) endpoints, their integration with the local agent environment, and how they are securely exposed.

1. Core Architecture #

The system utilizes two primary user-space applications hosted via systemd user services to expose visualization and management layers for active agents.

Pi Agent Dashboard: Serves the UI for managing agents, inspecting sessions, and interacting with the local Pi-AI workspace.
OMP Stats Dashboard: A secondary telemetry visualizer running omp stats.

2. Port and Firewall Configuration #

Backend Port Assignments #

Pi Dashboard backend is bound to 0.0.0.0:45433 (modified via systemd).
OMP Stats backend is bound to :::45434 (modified via systemd).

Nginx Reverse Proxy (Frontend) #

To implement a robust, basic authentication layer without relying on external OAuth providers, Nginx is deployed as a reverse proxy: