Limitations and known issues - php-tuf/composer-stager GitHub Wiki

Everywhere

  1. rsync is required.

  2. Many types of hard links and soft links (symlinks) are not supported. See details and rationale.

  3. Having Composer installed as a PHAR, e.g., composer.phar, is not support. See https://github.com/php-tuf/composer-stager/issues/356. (Work around the issue by renaming your executable to composer (no extension) or adding a symlink to it named composer in your $PATH.)

  4. Having the active and staging directories both in the temp directory is not supported.

  5. Syncing via remote protocols such as scp:// is not supported.

  6. Not all services do anything with the output callback.

Windows-specific

  1. The active and staging directories cannot be nested one inside the other.

  2. The active and staging directories cannot be on separate volumes. This may prevent use of the temp directory. It may be possible to work around this limitation by creating a symlink on one volume that points to the other directory across the volume boundary, but this has not been tested and is not officially supported.

  3. Composer Stager is tested with https://community.chocolatey.org/packages/rsync on Windows. No other version is officially supported.