stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
fcb5ffe25d489cd3452eaa2093c3ce1fef61d926
git.stella-ops.org/docs2/operations/install-deploy.md
master fcb5ffe25d feat(scanner): Complete PoE implementation with Windows compatibility fix 
- Fix namespace conflicts (Subgraph → PoESubgraph)
- Add hash sanitization for Windows filesystem (colon → underscore)
- Update all test mocks to use It.IsAny<>()
- Add direct orchestrator unit tests
- All 8 PoE tests now passing (100% success rate)
- Complete SPRINT_3500_0001_0001 documentation

Fixes compilation errors and Windows filesystem compatibility issues.
Tests: 8/8 passing
Files: 8 modified, 1 new test, 1 completion report

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-23 14:52:08 +02:00

1.1 KiB
Raw Blame History

Install and deploy

Prerequisites (baseline)

  • Linux host with sufficient CPU, memory, and disk for SBOM and artifact storage.
  • Docker Compose or Kubernetes (Helm) for deployment.
  • TLS termination for external access.

Required infrastructure

  • PostgreSQL (single cluster, schema isolation per module).
  • Valkey for cache, queues, and streams.
  • RustFS for content-addressed artifacts.

Optional infrastructure

  • Rekor mirror for transparency log anchoring.
  • Fulcio or KMS-backed signing provider.
  • NATS JetStream as an alternative queue and stream transport.

Deployment models

  • Compose profiles for single-node and lab environments.
  • Helm charts for multi-node and HA deployments.
  • Air-gap deployment via Offline Kit (see operations/airgap.md).

Configuration hierarchy

  1. Environment variables
  2. appsettings.{Environment}.json
  3. appsettings.json
  4. YAML overlays under etc/

Operational baselines

  • Enforce non-root containers and read-only filesystems where possible.
  • Use digest-pinned images for releases.
  • Keep clocks synchronized and use UTC everywhere.