This repository has been archived by the owner on Jan 21, 2020. It is now read-only.
forked from 19FT/NFDevelopmentMode
-
Notifications
You must be signed in to change notification settings - Fork 25
Use symlink instead of copy for easier distribution of config changes ? #27
Comments
This causes issues on Windows and IBM i Series, unfortunately, which is why we use the copy approach. |
Symlink are available in NTFS starting with Windows Vista. And apparently also available on IBM i Series. Would you please tell us more about what kind of issue there was ? I couldn't find anything |
So what about enabling symlink only on whitelisted OS, such as Linux and macOS ? would you accept a PR for that ? |
@PowerKiKi If it is not a problem to you please create PR with this feature and then we all can see it and discuss it there. I'd like this functionality, it will be much nicer to have symlinks. Thanks! |
PowerKiKi
added a commit
to PowerKiKi/zf-development-mode
that referenced
this issue
Mar 2, 2017
This makes the distribution of new development configuration much easier, since after a `git pull` we don't have to disable and re-enable developement mode anymore. Changes will be picked up automatically on supported OSes (Linux, Unix and macOS) Closes zfcampus#27
PowerKiKi
added a commit
to PowerKiKi/zf-development-mode
that referenced
this issue
Mar 2, 2017
This makes the distribution of new development configuration much easier, since after a `git pull` we don't have to disable and re-enable developement mode anymore. Changes will be picked up automatically on supported OSes (Linux, Unix and macOS) Closes zfcampus#27
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Would there be any interest in a PR that would replace the file copy by a symlink instead ?
The obvious advantage is that it makes distribution of new development configuration much easier. As of now we have to git push the config, and then tell everybody to
./vendor/bin/zf-development-mode disable && ./vendor/bin/zf-development-mode enable
, which is both unintuitive and error prone.If you think it would get merged, then I'll submit a PR for that.
The text was updated successfully, but these errors were encountered: