Composer Package Registry
Publish Composer packages for your user or organization.
Requirements
To work with the Composer package registry, you can use Composer to consume and a HTTP upload client like curl
to publish packages.
Publish a package
To publish a Composer package perform a HTTP PUT operation with the package content in the request body.
The package content must be the zipped PHP project with the composer.json
file.
You cannot publish a package if a package of the same name and version already exists. You must delete the existing package first.
Parameter | Description |
---|---|
owner | The owner of the package. |
If the composer.json
file does not contain a version
property, you must provide it as a query parameter:
Example request using HTTP Basic authentication:
Or specify the package version as query parameter:
If you are using 2FA or OAuth use a personal access token instead of the password.
The server responds with the following HTTP Status codes.
HTTP Status Code | Meaning |
---|---|
201 Created | The package has been published. |
400 Bad Request | The package is invalid. |
409 Conflict | A package file with the same combination of parameters exists already. |
Configuring the package registry
To register the package registry you need to add it to the Composer config.json
file (which can usually be found under <user-home-dir>/.composer/config.json
):
To access the package registry using credentials, you must specify them in the auth.json
file as follows:
Parameter | Description |
---|---|
owner | The owner of the package. |
username | Your Forgejo username. |
password | Your Forgejo password or a personal access token. |
Install a package
To install a package from the package registry, execute the following command:
Optional you can specify the package version:
Parameter | Description |
---|---|
package_name | The package name. |
package_version | The package version. |