-
Task
-
Resolution: Fixed
-
Should have
-
None
-
None
-
3
-
Dev Tools
-
Sprint #138, Sprint #139, Sprint #140, Sprint #141, Sprint #142, Sprint #143, Sprint #144, Sprint #145, Sprint #146, Sprint #147, Sprint #148, Sprint #149, Sprint #150, Sprint #151, Sprint #152, Sprint #153, Sprint #154, Sprint #155
Currently there is one big volume containing the entire wordpress directory. It would be better if there were separate volumes for the repositories that are developed.
- We can optimize each volume separately, so we can reduce the amount of disk usage resulting from syncing file changes inside the volumes. That will probably improve the speed of local development.
- We can more easily reset the environment without losing data (uncommitted changes, git stashes, ...).
Tasks
- Check if impact can be measures and if possible measure before and after changes
- Determine how many volumes we need and split it up - exclude cache
- Configure each volume to their optimal config, see article: https://docs.docker.com/docker-for-mac/osxfs-caching/#performance-implications-of-host-container-file-system-consistency
- relates to
-
PLANET-4601 Fix issues in local development (to be broken into smaller tickets)
- CLOSED
-
PLANET-5967 Investigate folder structure flexibility
- CLOSED
-
PLANET-5483 make npm/node persistent to our docker-compose dev images
- CLOSED
-
PLANET-5967 Investigate folder structure flexibility
- CLOSED