Closed mattdurant closed 1 month ago
@mattdurant Will keep this PR open for now for folks to find. Unsure whether we want to officially support this solution just yet until we explore all the options i.e. figure out what's the "nicest" dev experience for a new contributor
Closing as stale. For folks looking at this, if this PR is relevant to you, please open a new issue. Thanks!
Description
Created these "nohotload" variants of the docker-compose.dev.yml and Dockerfile from frontend/ for Windows or other devs that are in an environment where hard links on a Docker mount do not work either due to their OS or filesystem.
For example, on Windows using Windows Subsystem for Linux (wsl), Docker mounts to Windows filesystems are handled under the hood through CIFS shares, which do not support hard links or file system change monitoring, so hotloading would not work for next.js
Related Tickets & Documents
N/A
Screenshots/Recordings
N/A
Steps to QA
Try the out of the box dev files on a Windows environment and the issue is readily apparent. Start the environment using: docker compose -f docker-compose.yml -f docker-compose.dev.nohotload.yml build --no-cache, and then docker compose -f docker-compose.yml -f docker-compose.dev.nohotload.yml up -d
[optional] What gif best describes this PR?