In what type of project did the bug occur?
api-microservice
Describe the bug
The Docker Compose configuration doesn't mount the entire project as a volume. When migrations are generated inside the container, they only exist in the container filesystem and are not persisted to the host. This results in an empty migrations/versions folder locally.
To Reproduce
- Generate template with default options
- Run migration generation command in container
- Check local migrations/versions folder
Expected result
Migrations generated inside the container should be visible in the local filesystem so they can be committed to version control.
Actual result
Empty migrations/versions folder
Suggested solution
Add the following volume mounts to docker-compose
volumes:
- .:/root_project
- /root_project/.venv
Environment (please complete the following information):
- OS: Windows 11
- Execution method: docker
- Python version: 3.13
In what type of project did the bug occur?
api-microservice
Describe the bug
The Docker Compose configuration doesn't mount the entire project as a volume. When migrations are generated inside the container, they only exist in the container filesystem and are not persisted to the host. This results in an empty migrations/versions folder locally.
To Reproduce
Expected result
Migrations generated inside the container should be visible in the local filesystem so they can be committed to version control.
Actual result
Empty migrations/versions folder
Suggested solution
Add the following volume mounts to docker-compose
Environment (please complete the following information):