-
Notifications
You must be signed in to change notification settings - Fork 188
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.
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
Avoid to change path of composer.json #114
Comments
There is already a PR for this : #115 A better way is to set
This rule allow all dev branches like I thought of putting |
I like the idea of allowing all dev branches, however I tested with your same package monolog/monolog. The package was downloaded in packages folder but in vendor is not symlinked. Screenshot: But using Then I tested with custom package MyVendor/MyPackage and I can see in composer:
There is still full URL in repositories. If I move to server, I need to change composer.json What I mean here is that URL is rather like this:
but also like this:
Last doesn't require to edit for each package the "repositories", like now you have for each package:
|
I see and you're right. In one of my other PR I propose to set the path of the folder in the configuration file My first idea was to set a relative path here instead of the full one (with the call to basepath() ). But I'm agree, the simpliest way is to set only one repository rule with I'm just waiting now to see if my PR will be merged or not, after that I can do another PR for the "unique rule" |
@sebastienheyd did you create a PR for this, actually I was not able to locate the same. |
I'm not sure if this is the same or a different issue. Im working in WSL with a Docker container providing my webserver.
Because my webserver mounts
When I manually change, bother WSL & the webserver are happy. I think |
Right now in composer.json path are added with full path of local environment which should be changed when you move project.
Now is:
But better would be:
and in require:
What do you think?
The text was updated successfully, but these errors were encountered: