Summary
The container image definition still assumes a seed.py file and a SQLite runtime, but the repo uses DynamoDB and no seed.py exists at the root.
Evidence
- File: Dockerfile:14
- COPY config.py run.py seed.py ./ references seed.py, which is absent.
- Dockerfile:17-26 creates /data and sets DATABASE_URL=sqlite:////data/app.db, which no longer matches the application architecture.
Impact
- Docker builds are misleading or broken depending on context.
- Local developer guidance diverges from the actual runtime model.
Expected outcome
Align the Docker image with the current Flask+DynamoDB architecture and remove stale SQLite assumptions.
Summary
The container image definition still assumes a seed.py file and a SQLite runtime, but the repo uses DynamoDB and no seed.py exists at the root.
Evidence
Impact
Expected outcome
Align the Docker image with the current Flask+DynamoDB architecture and remove stale SQLite assumptions.