Forge allows you to manage the "http-basic" portion of the selected server user's
auth.json Composer configuration file. The provided credentials are only stored on the server being managed by Forge - not in Forge itself.
The Composer credentials that you can manage on the server level will apply to all sites that are served by the same Ubuntu user account. For example, if you have two sites installed under the
forge user, both these sites will benefit from the globally stored credentials. If you need fine-grained control, please see the Packages documentation for sites.
If you have sites configured with user isolation, you will first need to select the appropriate server user. The
auth.json file is global within each individual server user account.
Additional credentials can be added by clicking the "Add Credentials" button. You need to provide:
Click "Save" in order to store these credentials in the user's global Composer configuration directory (
In order to remove Composer credentials, you can click on the red X button.
After removing credentials, you must click "Save" in order to update the credentials configuration on the server.
Any credentials that are shown on the screen can be updated with any new adequate value.
After updating the credential, you must click "Save" in order to update the credentials configuration on the server.
The ability to manage a server's Composer packages is determined by the
server:manage-packages permission. This permission will also allow the circle member to manage a site's Composer packages too.