public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Capitalize composer name occurrences

pull/9250/head
Frank Prins 2020-10-05 21:13:02 +02:00
parent 78f9dd73ce
commit 5b34a61b4a
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/articles/authentication-for-private-packages.md
View File

@ -11,9 +11,9 @@ package(s).
# Authentication principles
Whenever composer encounters a protected composer repository it will try to authenticate
Whenever Composer encounters a protected Composer repository it will try to authenticate
using already defined credentials first. When none of those credentials apply it will prompt
for credentials instead otherwise overridden and save those (or a token if composer is able
for credentials instead otherwise overridden and save those (or a token if Composer is able
to retrieve one).
|type|Generated by Prompt?|
@ -43,7 +43,7 @@ command line or manually edit or create it.
If you don't want to supply credentials for every project you work on, storing your credentials
globally might be a better idea. These credentials are stored in a global `auth.json` in your
composer home directory.
Composer home directory.
### Command line global credential editing
@ -124,7 +124,7 @@ composer config [--global] --editor --auth
For the inline http-basic authentication method the credentials are not stored in a separate
`auth.json` in the project or globally, but in the `composer.json` or global configuration
in the same place where the composer repository definition is defined.
in the same place where the Composer repository definition is defined.
### Command line inline http-basic