# MeshCentral Workspace This repository collects Christ IT's MeshCentral-related work in one place. The workspace is intentionally source-first. It contains the code we own around MeshCentral operations, WordPress control, and MeshCentral plugin distribution. A full upstream MeshCentral checkout should stay outside this repository unless a specific patch or fork is being maintained. ## Project Lanes ### WordPress Control `wordpress/plugins/mesh-press/` MeshPress is the WordPress-side control plugin. It talks to the bridge service, caches fleet state, exposes MeshCentral group/device workflows, receives protected bridge events, and can forward useful lifecycle events into OmniLog. ### Bridge Service `bridge/meshpress-bridge/` MeshPress Bridge is the Node/Express service that runs beside MeshCentral. It talks to MeshCentral through `meshctrl`, exposes token-protected API routes to MeshPress, pushes fleet snapshots to WordPress, and gates higher-risk operations behind explicit environment flags. ### MeshCentral Plugins `meshcentral/plugins/` These are plugins that run inside MeshCentral itself. - `gracepress/` is the GracePress Catalog Connector for MeshCentral plugin delivery and diagnostics. - `gracepress-theme-studio/` is the first managed MeshCentral plugin, currently focused on theme profile editing. ### Current Distribution Artifacts `dist/current/` This folder keeps the current generated manifests, changelog copies, and MeshCentral facade files imported from the GracePress catalog. These are copied here as release evidence and migration reference. The long-term goal is for this workspace to own its own build/release scripts instead of depending on the GracePress workspace. ## External References `vendor/` Use this folder for notes about external dependencies or local clones. Do not commit a full upstream MeshCentral source tree by default. ## Current Migration Rule GracePress remains the active release/catalog source until this workspace has equivalent build and ship tooling. Do not delete the original GracePress copies until the new repository can build, package, and publish the same artifacts.