Move auth.json for composer into the root directory
See original GitHub issueThe composer extension moves composer.json
and composer.lock
into the root directory but not auth.json
if it exists.
auth.json
can be used to provide basic authentication credentials. By default composer searches them in COMPOSER_HOME
or besides the composer.json
. Since only the composer files are moved composer can’t find the auth.json
anymore. Therefore I suggest to move the file as well.
Is there a way to run a command before the buildpack/composer starts? I guess that can be used too but I haven’t found such a way yet.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Where is composer's global auth.json located? - Stack Overflow
Composer global files can usually be found at your home directory: In a *nix system that is: ~/.composer. auth.json should be in there...
Read more >Authentication for privately hosted packages and repositories
In this authentication storage method, an auth.json file will be present in the same folder as the projects' composer.json file. You can either...
Read more >How We Improved Composer Support For Our Premium ...
The auth.json file should be placed beside the composer.json file in your project on the server. This means it doesn't need to be ......
Read more >Installation - Laravel Nova
Once you have unzipped and placed the Nova source code within the appropriate directory, you are ready to update your composer.json file.
Read more >Specifying dependencies - App Engine - Google Cloud
You can declare dependencies for PHP in a standard composer.json file. For example: ... Create a file named auth.json in your project root...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ocean90 Thanks for bringing this up. We’ve addressed it, so keep an eye out for it in the next release, v4.3.53!
Prioritzed 🙂