Reviewed-on: https://codeberg.org/forgejo/website/pulls/323 # Conflicts: # v1.19/admin/command-line.md # v1.19/admin/config-cheat-sheet.md # v1.19/admin/database-preparation.md # v1.19/admin/email-setup.md # v1.19/admin/incoming-email.md # v1.19/admin/index.md # v1.19/admin/logging-documentation.md # v1.19/admin/reverse-proxy.md # v1.19/admin/seek-assistance.md # v1.19/admin/upgrade.md # v1.19/developer/code-forgejo-org.md # v1.19/developer/index.md # v1.19/index.md # v1.19/license.md # v1.19/user/agit-support.md # v1.19/user/api-usage.md # v1.19/user/authentication.md # v1.19/user/email-settings.md # v1.19/user/first-repository.md # v1.19/user/index.md # v1.19/user/issue-pull-request-templates.md # v1.19/user/issue-tracking-basics.md # v1.19/user/labels.md # v1.19/user/linked-references.md # v1.19/user/merge-message-templates.md # v1.19/user/oauth2-provider.md # v1.19/user/packages/cargo.md # v1.19/user/packages/chef.md # v1.19/user/packages/composer.md # v1.19/user/packages/conan.md # v1.19/user/packages/conda.md # v1.19/user/packages/container.md # v1.19/user/packages/generic.md # v1.19/user/packages/helm.md # v1.19/user/packages/index.md # v1.19/user/packages/maven.md # v1.19/user/packages/npm.md # v1.19/user/packages/nuget.md # v1.19/user/packages/pub.md # v1.19/user/packages/pypi.md # v1.19/user/packages/rubygems.md # v1.19/user/packages/storage.md # v1.19/user/packages/vagrant.md # v1.19/user/project.md # v1.19/user/protection.md # v1.19/user/push-options.md # v1.19/user/push-to-create.md # v1.19/user/repo-permissions.md # v1.19/user/webhooks.md # v1.19/user/wiki.md # v1.20/user/semver.md
3.7 KiB
title | license | origin_url |
---|---|---|
Composer Package Registry | Apache-2.0 | faa28b5a44/docs/content/doc/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]({{< relref "doc/developers/api-usage.en-us.md#authentication" >}}) 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 name and/or version are invalid or a package with the same name and version already exist. |
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. |