How ductura/server works
Ductura is a shared API server for AAI@EduHr sign-in, authorization, database-backed work, and background jobs. Its principal request path starts at the server entry point, passes through HTTP protections and contract-based routing, and reaches domain handlers; the documented functional check is opening a user’s own document while rejecting access to another’s. Evidence handling and its storage/signing options are major product capabilities, alongside sessions, administration, metrics, and downloads. Some area wiring is unsampled, so only documented or excerpt-supported relationships are drawn; dashed edges mark documented but unverified flow.
Main entry points: http HTTP area handlers · server.ts Server entry · service.ts Evidence service · router.ts API router
Components 22
Server runtime
- Server entry
server/server.ts - Runtime config
server/config/environment.ts - Runtime settings
server/settings/service.ts
HTTP and API
- Request pipeline
server/http/pipeline.ts - API router
server/http/router.ts - API contracts
server/contracts/routes/index.ts - HTTP area handlers
server/http - Problem responses
server/http/problem.ts
Identity and access
- Sessions and WebAuthn
server/session - Roles and permissions
server/roles/service.ts
Work and evidence
- Database access
server/database/index.ts - Domain rules
server/domain/index.ts - Evidence service
server/evidence/service.ts - Evidence storage
server/external/storage/port.ts - Evidence signing
server/external/keys/signing-key-provider.ts
Platform services
- Release downloads
server/downloads/service.ts - Metrics
server/metrics/service.ts - Support reports
server/support/service.ts - Backup
server/backup/service.ts - Account deletion
server/deletion/service.ts - Email integration
server/external/email/service.ts
Other components
- API client
Connections 22
- API client → Server entry: sends request
- Server entry → Runtime config: validates environment
server/server.ts - Server entry → Runtime settings: reads settings
server/server.ts - Server entry → Request pipeline: creates layers
server/server.ts - Server entry → HTTP area handlers: mounts handlers
server/server.ts - Request pipeline → HTTP area handlers: gates requests
server/http/pipeline.ts - API router → API contracts: matches contracts
server/http/router.ts - API router → Problem responses: sends errors
server/http/router.ts - Sessions and WebAuthn → Database access: uses actor access
server/session/index.ts - HTTP area handlers → Sessions and WebAuthn: authenticates requests
- HTTP area handlers → Roles and permissions: checks permissions
- Evidence service → Database access: uses persistence
server/evidence/service.ts - Evidence service → Domain rules: uses domain rules
server/evidence/service.ts - Evidence service → Evidence storage: uses payload storage
server/evidence/service.ts - Evidence storage → Evidence signing: configures S3 credentials
- HTTP area handlers → Evidence service: serves evidence requests
- HTTP area handlers → Release downloads: serves release requests
- HTTP area handlers → Metrics: serves metrics requests
- HTTP area handlers → Support reports: serves support requests
- HTTP area handlers → Backup: serves backup requests
- HTTP area handlers → Account deletion: serves deletion requests
- HTTP area handlers → Email integration: serves email requests