Antigravity 00004ce433 feat(infra): create staging docker-compose and environment configuration (#67)
This pull request introduces a production-grade, security-hardened Docker Staging environment configuration for **NexusReader**, prepared directly from the `develop` branch.

### 🚀 Key Additions

1. **`docker-compose.stage.yml`**:
   - Deploys five isolated containers (`nexus-web-stage`, `nexus-db-stage`, `nexus-qdrant-stage`, `nexus-neo4j-stage`) inside a dedicated `nexus-stage` bridge network.
   - Sets non-conflicting port mappings to allow staging to run concurrently with other environments on the same host (e.g., Web on `5080`, Postgres on `5438`, Neo4j HTTP on `7488`).
   - Configures robust container healthchecks (`curl` for Qdrant, `wget` for Neo4j, `pg_isready` for Postgres).
   - Maps dedicated named persistent volumes for databases (`pgdata_stage`, `qdrant_stage_data`, `neo4j_stage_data`) to prevent data loss.
   - Maps separate persistent volumes specifically for dynamic web uploads (`stage_www_uploads` for EPUBs, `stage_www_covers` for covers) without overriding the compiled static web client files.

2. **`.env.stage.template`**:
   - A clean deployment environment template providing a blueprint of all variables.
   - Copied to `.env.stage` locally during deployment to inject secrets securely.
   - Mandates a secure `NEXUS_ADMIN_PASSWORD` (checked by `DbInitializer` for staging/production builds).

3. **`.gitignore`**:
   - Explicitly ignores local environment configurations (such as `.env.stage`) to prevent accidentally committing credentials, while keeping the `.env.stage.template` tracked.

---

### 🧪 Verification Performed

- **Docker Compose Validation**: Ran `docker compose -f docker-compose.stage.yml --env-file .env.stage config` successfully with zero configuration or parsing errors.
- **Solution Compilation**: Ran `dotnet build NexusReader.slnx --no-restore` from root — **SUCCESS** with `0` compile errors.
- **Automated Tests**: Ran `dotnet test --no-restore` — **SUCCESS** (all 20/20 unit tests passed).

---------

Co-authored-by: Marek Jasiński <jasins.marek@gmail.com>
Reviewed-on: #67
Co-authored-by: Antigravity <antigravity@google.com>
Co-committed-by: Antigravity <antigravity@google.com>
2026-06-01 17:27:34 +00:00
2026-05-25 14:02:56 +02:00

📖 Nexus Reader

Nexus Reader is a state-of-the-art, cross-platform Blazor .NET 10 immersive e-book reader, powered by Native AOT, Clean Architecture, CQRS, and interactive D3.js Relationship Graphs built on vector-based AI semantics.


Features & Architecture Highlights

📁 Ingestion & Description persistence

  • Extracted and persistent book descriptions from EPUB package metadata during book ingestion.
  • The Description field propagates cleanly from the Ebook entity through Mapster to LastReadBookDto and UserProfileDto.
  • Implemented deep-link route activation: /reader/{bookId}?chapter=N.
  • Allows instant resume of reading session coordinates and loads the specific chapter chapter directly via URL query parameters.

🛡️ Downstream AI Resilience

  • Standard resilience engine in DependencyInjection.cs utilizing the Polly package (ai-retry).
  • Automatically intercepts, handles, and retries on both rate-limits (429 Too Many Requests) and downstream capacity overloads (503 ServiceUnavailable / high demand).

⚙️ Concurrent Request Deduplication

  • Multi-client InteractiveAuto Blazor circuit synchronization is backed by a thread-safe active task registry in KnowledgeService which ensures that identical concurrent requests await a single shared task instance, eliminating redundant LLM queries.

🛠️ Build & Verification Gate

Ensure the dotnet workload matches the active SDK, and compile the full solution utilizing:

dotnet build NexusReader.slnx --no-restore

Run test suite:

dotnet test --no-restore
S
Description
No description provided
Readme 16 MiB
Languages
C# 46.2%
HTML 25.8%
CSS 23%
JavaScript 4.1%
Shell 0.8%
Other 0.1%