Symlinks in Windows
Nanobox launches your app in a virtualized Linux environment and into which it mounts your local codebase. Creating symlinks in a codebase that mounted into a Linux environment, but actually resides in a Windows host filesystem can be tricky.
Windows and Linux/Unix have completely separate implementations for creating symlinks. Symlinks created in a Linux environment will not be honored by Windows and vice versa.
In order for symlinks created in Nanobox to work on a Windows host, there needs to be a "translation" layer. The
mfsymlinks option available when creating a CIFS (the mounting technology used in Windows) provides this layer.
Enable mfsymlinks in Your Nanobox Config
To enable mfsymlinks, use
nanobox config to set
nanobox config set netfs_mount_opts mfsymlinks
Information is also available in the Configuring Nanobox documentation.
Caveats with mfsymlinks
There are important things to know when using
Keep Symlink'd Files out of Version Control
If you create symlinks on Windows and then commit it into your source code, no other operating system will recognized it and it will cause issues for collaborators.
Don't commit symlinks to version control. All other collaborators need to create the symlinks themselves.
Reach out to firstname.lastname@example.org and we'll try to help.