Task #8056

Remove configuration option for mirrorMode

Added by Robert Lemke almost 10 years ago. Updated almost 8 years ago.

Should have
Target version:
Start date:
Due date:
% Done:


PHP Version:
Has patch:


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

Related issues

Related to TYPO3.Flow - Bug #8432: Fix Symlink support for Windows OS Resolved 2010-06-22
Related to TYPO3.Flow - Feature #11421: Allow linking of resources directories for mirror mode link Resolved 2010-12-12
Related to TYPO3.Flow - Task #11683: symlink() is not working on Windows XP Resolved 2010-12-24
Related to TYPO3.Flow - Feature #39253: Remove mirroring mode option and code Accepted 2012-07-25

Associated revisions

Revision d199532e (diff)
Added by Robert Lemke over 9 years ago

[~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
are used.

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

Change-Id: I2ca87862ded4d719bfc2776da2837e33645f4ab1


#1 Updated by Karsten Dambekalns over 9 years ago

  • Target version set to 1.0 alpha 14
  • Start date deleted (2010-06-04)

#2 Updated by Christopher Hlubek over 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.

#3 Updated by Karsten Dambekalns almost 9 years ago

  • Target version changed from 1.0 alpha 14 to 1230

#4 Updated by Karsten Dambekalns over 8 years ago

  • Target version deleted (1230)

#5 Updated by Karsten Dambekalns almost 8 years ago

  • Status changed from New to Closed
  • Assignee set to Karsten Dambekalns
  • Has patch set to No

Also available in: Atom PDF