Paul Payne
f5a030fd44
- Auto-generate random 32-char bearer token on first startup, stored in secrets.yaml as api.bearerToken - BearerAuthMiddleware checks Authorization: Bearer <token> on all /api/ endpoints except /health, /health/reconcile, /events (SSE), and non-API paths (frontend static files) - Development mode (WILD_CENTRAL_ENV=development) skips auth entirely - Web app ApiClient: add setToken/clearToken/hasToken methods, persist token in localStorage, automatically include Authorization header on all API requests - Token can be found in secrets.yaml for CLI/automation use
Wild Central Web App
The Wild Central Web App is a web-based interface for managing Wild Central and its connected services. It allows users to configure networking (DNS, gateway, VPN, firewall, TLS), manage Wild Cloud instances, deploy applications, and monitor resources.
Prerequisites
Before starting the web app, ensure the Wild Central API is running:
cd ..
make dev
The API should be accessible at http://localhost:5055.
Development
Initial Setup
- Copy the example environment file:
cp .env.example .env
- Update
.envif your API is running on a different host/port:
VITE_API_BASE_URL=http://localhost:5055
- Install dependencies:
pnpm install
- Start the development server:
pnpm run dev
The web app will be available at http://localhost:5173 (or the next available port).
Other Scripts
pnpm run build # Build the project
pnpm run lint # Lint the codebase
pnpm run preview # Preview the production build
pnpm run type-check # Type check the codebase
pnpm run test # Run tests
pnpm run test:ui # Run tests with UI
pnpm run test:coverage # Run tests with coverage report
pnpm run build:css # Build the CSS using Tailwind
pnpm run check # Run lint, type-check, and tests
Environment Variables
VITE_API_BASE_URL
The base URL of the Wild Central API.
- Default:
http://localhost:5055 - Example:
http://192.168.1.100:5055 - Usage: Set in
.envfile (see.env.examplefor template)