stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

setup and mock fixes

Browse Source
This commit is contained in:
master
2026-02-21 20:14:23 +02:00
parent 1edce73165
commit a29f438f53
29 changed files with 1624 additions and 721 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
docs/quickstart.md
View File

@@ -22,7 +22,7 @@ git clone <your-gitea-instance>/stella-ops/stella-ops.git
cd stella-ops
```
## 2. Run the setup script
## 2. Run setup
**Windows (PowerShell 7):**
@@ -36,33 +36,50 @@ cd stella-ops
./scripts/setup.sh
```
The script will:
The setup script will:
- Verify all prerequisites are installed
- Offer to add hosts file entries (50 services need unique loopback IPs)
- Create `.env` from the example template (works out of the box, no editing needed)
- Start infrastructure (PostgreSQL, Valkey, RustFS)
- Build .NET solutions and Docker images
- Launch the full platform
- Launch the full platform stack (`docker-compose.stella-ops.yml`)
- Run health checks and report status
### Infrastructure only (faster)
To skip builds and just start infrastructure:
To skip builds and only start infrastructure:
```powershell
.\scripts\setup.ps1 -InfraOnly # Windows
./scripts/setup.sh --infra-only # Linux/macOS
```
## 3. Open the platform
## 3. First 30 minutes path
Once setup completes, open **https://stella-ops.local** in your browser.
Accept the self-signed certificate warning on first visit.
1. Start platform quickly (reuse existing images):
```powershell
.\scripts\setup.ps1 -SkipBuild -SkipImages
```
2. Confirm service health:
```powershell
docker compose -f devops/compose/docker-compose.stella-ops.yml ps
```
3. Preview demo seeding:
```powershell
dotnet run --project src/Cli/StellaOps.Cli/StellaOps.Cli.csproj -- `
admin seed-demo --dry-run `
--connection "Host=127.1.1.1;Port=5432;Database=stellaops_platform;Username=stellaops;Password=stellaops"
```
4. Seed demo data:
```powershell
dotnet run --project src/Cli/StellaOps.Cli/StellaOps.Cli.csproj -- `
admin seed-demo --confirm `
--connection "Host=127.1.1.1;Port=5432;Database=stellaops_platform;Username=stellaops;Password=stellaops"
```
5. Open **https://stella-ops.local**.
## What's running
After a full setup, you'll have 45+ services running locally:
After a full setup, you'll have 60+ services running locally:
| Service | URL | Purpose |
|---------|-----|---------|
@@ -72,16 +89,27 @@ After a full setup, you'll have 45+ services running locally:
| Concelier | https://concelier.stella-ops.local | Advisory aggregation |
| PostgreSQL | db.stella-ops.local:5432 | Primary database |
| Valkey | cache.stella-ops.local:6379 | Cache and messaging |
| RustFS | s3.stella-ops.local:8333 | S3-compatible object storage |
Full service list: `devops/compose/docker-compose.stella-ops.yml`
Optional Sigstore services (`rekor-v2`, `rekor-cli`, `cosign`) are enabled only with:
```bash
docker compose -f devops/compose/docker-compose.stella-ops.yml --profile sigstore up -d
```
## Troubleshooting
**"stella-ops.local not found"** -- The hosts file entries are missing. Re-run the setup script and accept the hosts file installation, or manually append `devops/compose/hosts.stellaops.local` to your hosts file.
**Containers unhealthy** -- Check logs with `docker compose -f devops/compose/docker-compose.stella-ops.yml logs <service-name>`.
**Port conflicts** -- Override ports in `devops/compose/.env`. See `devops/compose/env/stellaops.env.example` for available port variables.
| Symptom | Meaning | Action |
|---------|---------|--------|
| `stella-ops.local` not found | Hosts entries missing | Re-run setup and accept hosts installation, or append `devops/compose/hosts.stellaops.local` manually |
| `health=starting` for RustFS during setup | Advisory startup lag | Wait 30-60 seconds and re-check `docker compose ... ps` |
| `stellaops-dev-rekor` restarting without `--profile sigstore` | Optional profile container from older runs | Non-blocking for default setup; ignore or clean old container |
| `SM remote service probe failed (localhost:56080)` in CLI | Optional China SM Remote plugin probe | Non-blocking for default crypto profile |
| `admin seed-demo --confirm` fails with `scheduler_exceptions_tenant_isolation already exists` | Outdated Scheduler migration scripts | Pull latest code and rerun seeding |
| Seed endpoint still returns HTTP 500 after patching source | Running old container image | Rebuild/restart platform image and retest |
| Port conflicts | Local process already using mapped port | Override in `devops/compose/.env` (`devops/compose/env/stellaops.env.example`) |
## Next steps