Remove configuration option for mirrorMode
The resource publisher can mirror resources either be creating symlinks or copying the files. This can be configured through the mirrorMode setting. The default of this setting is "copy" to guarantee that file publishing works on any system. What most people want though is "symlink" because it's much faster.
This task is about checking the possibility to remove this user setting and let FLOW3 autodetect which method to use. The detection mechanism should consider
- if the OS supports symlinks
- if the webserver is configured to actually follow symlinks
[~TASK][!!!] FLOW3: Make symlink mirror mode the default
The setting FLOW3:resource:publishing:fileSystem:mirrorMode
is now set to "link" by default which means that instead of
copying each resource file to the public directory, symlinks
It is not 100% clear yet, how systems not supporting symlinks
behave - if you experience any problems, please open an issue
with a good error description so we can take some precautions
Relates to: #8056
#2 Updated by Christopher Hlubek about 9 years ago
Since we are able to write configuration files we could think about doing some kind of "autosetup" in FLOW3. So we don't have to check abilities for every request but only on the first hit and then write the configuration. I think there are cases where you would want to use copy mode even if symlinks are available by the system.