Skip to content
centiceps

Run the devnet

The development network runs a real control plane, gateway backend, load-balanced gateway fleet, data stores, fixture upstream, and seeded API Bundles. Use it for authoring, deployment practice, trace sessions, and policy-chain smoke tests.

Prerequisites

Section titled “Prerequisites”
  • Docker with Compose support
  • PowerShell 7 for the bundled verification scripts
  • A clone of the Centiceps repository

Start the complete environment

Section titled “Start the complete environment”

From the repository root:

Terminal window
docker compose --project-directory . `
  -f deploy\compose\docker-compose.yml `
  -f deploy\devnet\docker-compose.devnet.yml `
  up --build -d

Check that the containers are running:

Terminal window
docker compose --project-directory . `
  -f deploy\compose\docker-compose.yml `
  -f deploy\devnet\docker-compose.devnet.yml `
  ps

Open the control plane

Section titled “Open the control plane”

Open http://127.0.0.1:5290/admin/ and sign in with the local-only bootstrap credentials:

client ID:     centiceps-admin
client secret: centiceps-admin-secret

Verify gateway traffic

Section titled “Verify gateway traffic”

The load-balanced gateway listens on port 5080:

Terminal window
.\deploy\devnet\smoke-devnet.ps1 -GatewayUrl http://127.0.0.1:5080

Run the optional local throughput lane:

Terminal window
.\deploy\devnet\smoke-devnet.ps1 `
  -GatewayUrl http://127.0.0.1:5080 `
  -Throughput `
  -Requests 250

Useful local endpoints

Section titled “Useful local endpoints”
URL Purpose
http://127.0.0.1:5290/admin/ Control-plane console
http://127.0.0.1:5080 Load-balanced gateway
http://127.0.0.1:8404 HAProxy statistics
http://127.0.0.1:15672 RabbitMQ management

Next, inspect your first API Bundle.