Privacy choices
This site may send the owner a minimal page-visit notice with page, browser, device type, and resolution. If you accept analytics, it can also remember an anonymous visit/session ID and collect richer engagement signals.
Read the privacy noticeThe VPS deployment stack — CMS and Alex OS run as separate systemd services behind Nginx on a single server.
The CMS runs on port 3005 and Alex OS on port 8010, both as systemd units on a CloudPanel-managed VPS. Deploy/ops tooling in the repo (start/stop/reset/snapshot/restore scripts) manages both processes.
The CMS and Alex OS now run as separate systemd services on a single CloudPanel VPS, with Nginx routing and a full suite of ops scripts in the repo.
What changed: one server, two services, clean separation
Alex CMS runs on port 3005 and Alex OS on port 8010 — each as its own systemd unit on a CloudPanel-managed VPS, with Nginx sitting in front of both. Keeping them as separate processes means one service crashing or restarting doesn't take down the other, and each can be managed independently.
Ops tooling lives in the repo
Start, stop, reset, snapshot, and restore scripts are checked into the repository alongside the code. That means deployment and recovery steps are documented by default — no tribal knowledge required to bring either service back up or roll back a bad deploy.