run-local

Boot the Nexus Gateway local stack with PostgreSQL, Valkey, and NATS via docker-compose.

21|3|Updated May 26, 2026
One-click install
npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill run-local-alphabitcore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-local
Source: https://github.com/AlphaBitCore/nexus-gateway/tree/main/.claude/skills/run-local
Command: npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill run-local-alphabitcore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bring up the full Nexus Gateway local stack from a clean clone—PostgreSQL, Valkey, and NATS—along with four Go services (Hub, Control Plane, AI Gateway, Compliance Proxy) and the Control Plane UI, providing a repeatable bootstrap for OSS contributors.

Core Features & Use Cases

  • End-to-end local environment bootstrap including DB, TLS, services, and UI
  • Guarded, self-healing startup with explicit error surfacing for common failures
  • Reproducible dev stack for onboarding, testing, and contribution workflows

Quick Start

Boot the local Nexus Gateway stack from a clean clone and verify all five services are listening on their documented ports with the UI available at http://localhost:3000.

Frequently Asked Questions about run-local

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bring up the Nexus Gateway local stack from a clean clone?

To bring up the local stack, run the bootstrap process which starts PostgreSQL, Valkey, and NATS via docker-compose, then initializes the Hub, Control Plane, AI Gateway, Compliance Proxy, and UI with environment variables and health checks.

What is the best way to bootstrap a local development environment for Nexus Gateway Go services?

The best way to bootstrap the dev environment is using a guarded, self-healing startup script that applies per-service -config flags, verifies ports, and runs health checks to ensure all five services are listening correctly.

Do I need docker-compose to run the local Nexus Gateway stack and its dependencies?

Yes, you need docker-compose to run the local Nexus Gateway stack because it orchestrates the required infrastructure dependencies, specifically PostgreSQL, Valkey, and NATS, alongside the application services.

Which services are included when I start the local Nexus Gateway environment?

Starting the local Nexus Gateway environment includes the Hub, Control Plane, AI Gateway, Compliance Proxy, and the Control Plane UI, providing a full end-to-end local development stack.

Why does my local Nexus Gateway startup fail before the UI is available at localhost:3000?

Startup failures before the UI is available at localhost:3000 often occur because environment variables are missing or per-service port verification and health checks failed during the bootstrap process.

Can I use this local stack setup for onboarding and testing Open Source Software contributions?

Yes, you can use this setup for onboarding and testing contributions because it provides a reproducible dev stack that enforces an end-to-end bootstrap from a clean clone.