W
William Gill
I develop websites and frequently need to have a "parallel" site when
making major changes. In the past I simply copied common asset
directories, but image directories are quite large. On my *nix systems I
could use symlinks to eliminate the duplication of these large files. I
am trying to use windows junctions but am running into a minor problem.
The junction source folder looks just like the target folder, so when
all changes are complete and there is no longer any need for the
duplicates it is easy to delete the junction thus deleting all files in
the target.
I have implemented the practice of changing the source icon to draw
attention to the fact it is not a regular folder, but it's still too
easy to do the damage. I have tried explicitly removing delete
permission, and it does not seem to help.
How can I protect the junction source from being deleted?
Any suggestions?
making major changes. In the past I simply copied common asset
directories, but image directories are quite large. On my *nix systems I
could use symlinks to eliminate the duplication of these large files. I
am trying to use windows junctions but am running into a minor problem.
The junction source folder looks just like the target folder, so when
all changes are complete and there is no longer any need for the
duplicates it is easy to delete the junction thus deleting all files in
the target.
I have implemented the practice of changing the source icon to draw
attention to the fact it is not a regular folder, but it's still too
easy to do the damage. I have tried explicitly removing delete
permission, and it does not seem to help.
How can I protect the junction source from being deleted?
Any suggestions?