...
Optional: Save authentication information in auth.json to avoid repeatedly typing it
Composer will ask you to do this for you usuallyon updates, however if not to avoid having to always fill your credentials, add an it is disabled you can create auth.json
file in your manually in one of the following ways:
Option A: Store your credentials in project directory:
Code Block | ||
---|---|---|
| ||
composer config http-basic.updates.ez.no <installation-key> <token-password> |
Option B: If you rather want to install it globally in COMPOSER_HOME directory for machine-wide use. The file looks like the following:
Code Block | ||||||
---|---|---|---|---|---|---|
| {
"config": {
"basic-auth": {
"
| |||||
composer config --global http-basic.updates.ez.no": { "username": "<installation-key>", "password": "<token password>" } } } } |
Using composer
Update workflow
<token-password> |
Update workflowUsing composer
This section describes a best practice for use of composer, essentially it suggests treating updates like other code/configuration/* changes on your project tackling them on a development machine before staging them for roll out on staging/production.
...