You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
92 lines
2.3 KiB
92 lines
2.3 KiB
---
|
|
title: "fix: docker-compose.yml references missing scheduler.py"
|
|
type: fix
|
|
status: active
|
|
date: 2026-04-24
|
|
---
|
|
|
|
# Fix: docker-compose.yml Missing scheduler.py
|
|
|
|
## Overview
|
|
|
|
`docker-compose.yml` defines a `scheduler` service that runs `python scheduler.py`, but no `scheduler.py` exists in the repo. This causes `docker-compose up` to fail for the scheduler service.
|
|
|
|
## Problem Frame
|
|
|
|
- The scheduler service is a deployment bug
|
|
- Either the file was never created, or it was removed and the compose file was not updated
|
|
- The `schedule` dependency in pyproject.toml suggests automated scheduling was intended
|
|
|
|
## Requirements Trace
|
|
|
|
- R1. docker-compose.yml must reference only existing files
|
|
- R2. If scheduling is desired, create scheduler.py; if not, remove the service
|
|
|
|
## Scope Boundaries
|
|
|
|
**Included:**
|
|
- Fix docker-compose.yml
|
|
|
|
**Excluded:**
|
|
- Implementing actual scheduling logic (unless user confirms)
|
|
|
|
## Implementation Units
|
|
|
|
- [ ] U1. **Determine scheduler intent**
|
|
|
|
**Goal:** Decide whether to create scheduler.py or remove the service.
|
|
|
|
**Requirements:** R1, R2
|
|
|
|
**Dependencies:** None
|
|
|
|
**Files:**
|
|
- Read: `docker-compose.yml`, `pyproject.toml`
|
|
|
|
**Approach:**
|
|
- Check if `schedule` dependency is used anywhere
|
|
- Check if there's a scheduling script under another name
|
|
- Decision: If scheduling is not implemented, remove the service for now and create a plan for it later
|
|
|
|
**Test expectation:** none — decision unit.
|
|
|
|
**Verification:**
|
|
- Clear decision documented in this plan
|
|
|
|
---
|
|
|
|
- [ ] U2. **Apply fix**
|
|
|
|
**Goal:** Make docker-compose.yml valid.
|
|
|
|
**Requirements:** R1
|
|
|
|
**Dependencies:** U1
|
|
|
|
**Files:**
|
|
- Modify: `docker-compose.yml`
|
|
|
|
**Approach:**
|
|
- Option A: Remove scheduler service (if scheduling is deferred)
|
|
- Option B: Create minimal scheduler.py (if scheduling is desired now)
|
|
|
|
**Test scenarios:**
|
|
- Integration: `docker-compose config` validates without error
|
|
- Happy path: `docker-compose up motief` works (existing service unchanged)
|
|
|
|
**Verification:**
|
|
- `docker-compose config` passes
|
|
- No reference to missing scheduler.py
|
|
|
|
---
|
|
|
|
## Risks & Dependencies
|
|
|
|
| Risk | Mitigation |
|
|
|------|------------|
|
|
| Removing service breaks someone's workflow | Only remove if confirmed unused; otherwise create stub |
|
|
|
|
## Sources & References
|
|
|
|
- `docker-compose.yml`
|
|
- `pyproject.toml` (schedule dependency)
|
|
|