Deploying a new Docker version currently wipes all data because data.json is not mounted outside the container.
Sub-tasks from TODO.md:
Introduce a /data directory for persistent storage
Approach:
Create a /data directory convention in the project
Update docker-compose.yml to mount a volume for /data
Move data.json (and any other persistent files) into the /data directory
Update all file paths in the server code that reference data storage
Document the volume mount in README for deployment instructions
## Feature: Persistent Data in Docker
**Source:** TODO.md lines 31-32
### Implementation Notes
Deploying a new Docker version currently wipes all data because `data.json` is not mounted outside the container.
**Sub-tasks from TODO.md:**
- [ ] Introduce a `/data` directory for persistent storage
**Approach:**
1. Create a `/data` directory convention in the project
2. Update `docker-compose.yml` to mount a volume for `/data`
3. Move `data.json` (and any other persistent files) into the `/data` directory
4. Update all file paths in the server code that reference data storage
5. Document the volume mount in README for deployment instructions
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Feature: Persistent Data in Docker
Source: TODO.md lines 31-32
Implementation Notes
Deploying a new Docker version currently wipes all data because
data.jsonis not mounted outside the container.Sub-tasks from TODO.md:
/datadirectory for persistent storageApproach:
/datadirectory convention in the projectdocker-compose.ymlto mount a volume for/datadata.json(and any other persistent files) into the/datadirectory