Initial public release
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
# ADR-006 — Job Processing
|
||||
|
||||
## Status
|
||||
Accepted for V1.
|
||||
|
||||
## Context
|
||||
Raster tiling, detection, segmentation, QA, and exports can take longer than a normal HTTP request.
|
||||
|
||||
## Decision
|
||||
Use Redis + RQ for V1 background jobs. Every long-running operation creates an `analysis_run` or `job` record, updates status, stores outputs, and emits events.
|
||||
|
||||
Supported statuses:
|
||||
|
||||
- pending,
|
||||
- queued,
|
||||
- running,
|
||||
- completed,
|
||||
- failed,
|
||||
- cancelled.
|
||||
|
||||
## Consequences
|
||||
The UI can show progress and status without blocking. RQ is easier than Celery for an initial solo/portfolio project.
|
||||
|
||||
## Non-goals
|
||||
No Kubernetes-native queues, no Airflow, no full workflow engine in V1.
|
||||
Reference in New Issue
Block a user