forgejo-federation/docs/content/doc/usage/packages/rpm.en-us.md
KN4CK3R 5968c63a11
Add Go package registry (#24687)
Fixes #7608

This PR adds a Go package registry usable with the Go proxy protocol.

![grafik](https://github.com/go-gitea/gitea/assets/1666336/328feb5c-3df2-4f9d-8eae-fe3126d14c37)
2023-05-14 23:38:40 +08:00

3.5 KiB

date title slug draft toc menu
2023-03-08T00:00:00+00:00 RPM Packages Repository packages/rpm false false
sidebar
parent name weight identifier
packages RPM 105 rpm

RPM Packages Repository

Publish RPM packages for your user or organization.

Table of Contents

{{< toc >}}

Requirements

To work with the RPM registry, you need to use a package manager like yum or dnf to consume packages.

The following examples use dnf.

Configuring the package registry

To register the RPM registry add the url to the list of known apt sources:

dnf config-manager --add-repo https://gitea.example.com/api/packages/{owner}/rpm.repo
Placeholder Description
owner The owner of the package.

If the registry is private, provide credentials in the url. You can use a password or a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}):

dnf config-manager --add-repo https://{username}:{your_password_or_token}@gitea.example.com/api/packages/{owner}/rpm.repo

You have to add the credentials to the urls in the rpm.repo file in /etc/yum.repos.d too.

Publish a package

To publish a RPM package (*.rpm), perform a HTTP PUT operation with the package content in the request body.

PUT https://gitea.example.com/api/packages/{owner}/rpm/upload
Parameter Description
owner The owner of the package.

Example request using HTTP Basic authentication:

curl --user your_username:your_password_or_token \
     --upload-file path/to/file.rpm \
     https://gitea.example.com/api/packages/testuser/rpm/upload

If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password. You cannot publish a file with the same name twice to a package. You must delete the existing package version first.

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 exist already in the package.

Delete a package

To delete a Debian package perform a HTTP DELETE operation. This will delete the package version too if there is no file left.

DELETE https://gitea.example.com/api/packages/{owner}/rpm/{package_name}/{package_version}/{architecture}
Parameter Description
owner The owner of the package.
package_name The package name.
package_version The package version.
architecture The package architecture.

Example request using HTTP Basic authentication:

curl --user your_username:your_token_or_password -X DELETE \
     https://gitea.example.com/api/packages/testuser/rpm/test-package/1.0.0/x86_64

The server responds with the following HTTP Status codes.

HTTP Status Code Meaning
204 No Content Success
404 Not Found The package or file was not found.

Install a package

To install a package from the RPM registry, execute the following commands:

# use latest version
dnf install {package_name}
# use specific version
dnf install {package_name}-{package_version}.{architecture}