Disallow auto-symlinking of shared files/folders

In contrast to DeployBot, DeployHQ auto-symlinks files and folders as part of the deployment process into their corresponding path in the release.

This could, and has, caused problems when symlinking files/folders to their correct path via SSH commands, which are run after DeployHQ auto-symlinks files/folders, DeployHQ auto-symlinks the same files/folders into:

• The wrong place, when the files/folders to be symlinked are in a different location to their eventual location in the release, requiring extra “cleanup” commands to be run to remove these files/folders from their auto-symlinked location.

• The correct place, resulting in manual symlink commands failing due to the files/folders already being present (granted, this is mainly an issue with SSH commands which have been migrated from DeployBot, rather than on new servers where we can accommodate for the auto-symlinking from the get-go).

• The correct place, but in error. For example, when a file/folder exists in a shared folder but shouldn’t be symlinked at all (and isn’t being symlinked manually). This one in particular has caused us some trouble by resulting in site downtime where a file was auto-symlinked into a place it shouldn’t be (and wasn’t being symlinked manually for exactly this reason).

Being able to disable auto-symlinking on a per-project or per-server basis would be fantastic, as we can then ensure we’re in full control of what’s being symlinked and where to via SSH commands, rather than having to dodge and ‘watch out for’ DeployHQ’s auto-symlinking process.