Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Symlinked files are not followed / always replaced #79

Open
cbrunnkvist opened this issue Jul 16, 2015 · 0 comments
Open

Symlinked files are not followed / always replaced #79

cbrunnkvist opened this issue Jul 16, 2015 · 0 comments

Comments

@cbrunnkvist
Copy link

When there is a symlink in place e.g. app/config/parameters.yml -> /somewhere/shared/config/env-parameters.yml, the symlink is removed and replaced by a file generated from scratch.

Wouldn't it make sense if it followed the symlink and treated content as content to matter where in the filesystem the eventual file happens to reside?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cbrunnkvist