Added another path option to reach autoload.php

[gailimov]

Same issue as described here.

There is no symlink in macOS, just a copy of executable which cannot locate autoloader. But if we, for example, create project inside Docker container using Alpine 3.10 as base image, it creates symlink to vendor/zfcampus/zf-development-mode/bin/zf-development-mode and everything works fine as expected.

• Are you fixing a bug?
  • Detail how the bug is invoked currently.
  • Detail the original, incorrect behavior.
  • Detail the new, expected behavior.
  • Base your feature on the master branch, and submit against that branch.

[michalbundyra]

LGTM 👍

[dennybrandes]

LGTM

[weierophinney]

This repository has been closed and moved to laminas/laminas-development-mode; a new issue has been opened at laminas/laminas-development-mode#1.

[weierophinney]

This repository has been moved to laminas/laminas-development-mode. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

• Squash all commits in your branch (git rebase -i origin/{branch})
• Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
• Run the laminas/laminas-migration tool on the code.
• Clone laminas/laminas-development-mode to another directory.
• Copy the files from the second bullet point to the clone of laminas/laminas-development-mode.
• In your clone of laminas/laminas-development-mode, commit the files, push to your fork, and open the new PR.
  We will be providing tooling via laminas/laminas-migration soon to help automate the process.