12abdfe81d
Implements FED-010: Agent Spawn via Federation feature that enables spawning and managing Claude agents on remote federated Mosaic Stack instances via COMMAND message type. Features: - Federation agent command types (spawn, status, kill) - FederationAgentService for handling agent operations - Integration with orchestrator's agent spawner/lifecycle services - API endpoints for spawning, querying status, and killing agents - Full command routing through federation COMMAND infrastructure - Comprehensive test coverage (12/12 tests passing) Architecture: - Hub → Spoke: Spawn agents on remote instances - Command flow: FederationController → FederationAgentService → CommandService → Remote Orchestrator - Response handling: Remote orchestrator returns agent status/results - Security: Connection validation, signature verification Files created: - apps/api/src/federation/types/federation-agent.types.ts - apps/api/src/federation/federation-agent.service.ts - apps/api/src/federation/federation-agent.service.spec.ts Files modified: - apps/api/src/federation/command.service.ts (agent command routing) - apps/api/src/federation/federation.controller.ts (agent endpoints) - apps/api/src/federation/federation.module.ts (service registration) - apps/orchestrator/src/api/agents/agents.controller.ts (status endpoint) - apps/orchestrator/src/api/agents/agents.module.ts (lifecycle integration) Testing: - 12/12 tests passing for FederationAgentService - All command service tests passing - TypeScript compilation successful - Linting passed Refs #93 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
80 lines
1.6 KiB
Markdown
80 lines
1.6 KiB
Markdown
# Quick Start
|
|
|
|
Get Mosaic Stack running in 5 minutes with Docker.
|
|
|
|
## Prerequisites
|
|
|
|
- Docker 24+ and Docker Compose 2.20+
|
|
- Git 2.x
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
# Clone repository
|
|
git clone https://git.mosaicstack.dev/mosaic/stack mosaic-stack
|
|
cd mosaic-stack
|
|
|
|
# Copy environment file
|
|
cp .env.example .env
|
|
|
|
# Start all services
|
|
docker compose up -d
|
|
|
|
# Run migrations
|
|
docker compose exec api pnpm prisma migrate deploy
|
|
|
|
# Seed development data (optional)
|
|
docker compose exec api pnpm prisma:seed
|
|
```
|
|
|
|
## Verify Installation
|
|
|
|
```bash
|
|
# Check API health
|
|
curl http://localhost:3001/health
|
|
|
|
# Expected response:
|
|
# {"status":"ok","timestamp":"...","uptime":...}
|
|
|
|
# View logs
|
|
docker compose logs -f api
|
|
```
|
|
|
|
## What's Running?
|
|
|
|
| Service | Port | Purpose |
|
|
| ---------- | ---- | ------------------------ |
|
|
| API | 3001 | NestJS backend |
|
|
| PostgreSQL | 5432 | Database |
|
|
| Valkey | 6379 | Cache (Redis-compatible) |
|
|
|
|
## Next Steps
|
|
|
|
1. **Configure Authentication** — See [Configuration → Authentik](../3-configuration/2-authentik.md)
|
|
2. **Explore the API** — Check [API Reference](../../4-api/README.md)
|
|
3. **Start Developing** — Read [Development → Workflow](../../2-development/1-workflow/1-branching.md)
|
|
|
|
## Troubleshooting
|
|
|
|
**Port already in use:**
|
|
|
|
```bash
|
|
# Stop existing services
|
|
docker compose down
|
|
|
|
# Check what's using the port
|
|
lsof -i :3001
|
|
```
|
|
|
|
**Database connection failed:**
|
|
|
|
```bash
|
|
# Check PostgreSQL is running
|
|
docker compose ps postgres
|
|
|
|
# View PostgreSQL logs
|
|
docker compose logs postgres
|
|
```
|
|
|
|
For detailed installation options, see [Installation → Local Setup](../2-installation/2-local-setup.md).
|