0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-11-21 17:36:59 -05:00
forgejo-docs/docs/user/packages/composer.md
Earl Warren 6aa9b491a0 sync with Gitea e865de1e9d65dc09797d165a51c8e705d2a86030
cd docs
git diff d3982bcd814bac93e3cbce1c7eb749b17e413fbd..e865de1e9d65dc09797d165a51c8e705d2a86030 -- $(find . -type f -name '*en-us*')
2024-04-23 07:16:10 +00:00

3.6 KiB

title license origin_url
Composer Package Registry Apache-2.0 e865de1e9d/docs/content/usage/packages/composer.en-us.md

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.

PUT https://forgejo.example.com/api/packages/{owner}/composer
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:

PUT https://forgejo.example.com/api/packages/{owner}/composer?version={x.y.z}

Example request using HTTP Basic authentication:

curl --user your_username:your_password_or_token \
     --upload-file path/to/project.zip \
     https://forgejo.example.com/api/packages/testuser/composer

Or specify the package version as query parameter:

curl --user your_username:your_password_or_token \
     --upload-file path/to/project.zip \
     https://forgejo.example.com/api/packages/testuser/composer?version=1.0.3

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):

{
  "repositories": [
    {
      "type": "composer",
      "url": "https://forgejo.example.com/api/packages/{owner}/composer"
    }
  ]
}

To access the package registry using credentials, you must specify them in the auth.json file as follows:

{
  "http-basic": {
    "forgejo.example.com": {
      "username": "{username}",
      "password": "{password}"
    }
  }
}
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:

composer require {package_name}

Optional you can specify the package version:

composer require {package_name}:{package_version}
Parameter Description
package_name The package name.
package_version The package version.