2022-03-30 08:42:47 +00:00
---
date: "2021-07-20T00:00:00+00:00"
title: "Package Registry"
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 03:33:41 +00:00
slug: "overview"
2023-07-26 04:53:13 +00:00
sidebar_position: 1
2022-03-30 08:42:47 +00:00
draft: false
toc: false
menu:
sidebar:
parent: "packages"
name: "Overview"
2023-07-26 04:53:13 +00:00
sidebar_position: 1
2023-02-25 09:56:02 +00:00
identifier: "packages-overview"
2022-03-30 08:42:47 +00:00
---
# Package Registry
2022-05-29 18:10:21 +00:00
Starting with Gitea **1.17** , the Package Registry can be used as a public or private registry for common package managers.
2022-03-30 08:42:47 +00:00
## Supported package managers
The following package managers are currently supported:
| Name | Language | Package client |
| ---- | -------- | -------------- |
2023-07-26 04:53:13 +00:00
| [Alpine ](usage/packages/alpine.md ) | - | `apk` |
| [Cargo ](usage/packages/cargo.md ) | Rust | `cargo` |
| [Chef ](usage/packages/chef.md ) | - | `knife` |
| [Composer ](usage/packages/composer.md ) | PHP | `composer` |
| [Conan ](usage/packages/conan.md ) | C++ | `conan` |
| [Conda ](usage/packages/conda.md ) | - | `conda` |
| [Container ](usage/packages/container.md ) | - | any OCI compliant client |
| [CRAN ](usage/packages/cran.md ) | R | - |
| [Debian ](usage/packages/debian.md ) | - | `apt` |
| [Generic ](usage/packages/generic.md ) | - | any HTTP client |
| [Go ](usage/packages/go.md ) | Go | `go` |
| [Helm ](usage/packages/helm.md ) | - | any HTTP client, `cm-push` |
| [Maven ](usage/packages/maven.md ) | Java | `mvn` , `gradle` |
| [npm ](usage/packages/npm.md ) | JavaScript | `npm` , `yarn` , `pnpm` |
| [NuGet ](usage/packages/nuget.md ) | .NET | `nuget` |
| [Pub ](usage/packages/pub.md ) | Dart | `dart` , `flutter` |
| [PyPI ](usage/packages/pypi.md ) | Python | `pip` , `twine` |
| [RPM ](usage/packages/rpm.md ) | - | `yum` , `dnf` , `zypper` |
| [RubyGems ](usage/packages/rubygems.md ) | Ruby | `gem` , `Bundler` |
2024-02-08 08:53:44 +00:00
| [Swift ](usage/packages/swift.md ) | Swift | `swift` |
2023-07-26 04:53:13 +00:00
| [Vagrant ](usage/packages/vagrant.md ) | - | `vagrant` |
2022-03-30 08:42:47 +00:00
**The following paragraphs only apply if Packages are not globally disabled!**
2022-04-01 15:31:40 +00:00
## Repository-Packages
A package always belongs to an owner (a user or organisation), not a repository.
To link an (already uploaded) package to a repository, open the settings page
on that package and choose a repository to link this package to.
The entire package will be linked, not just a single version.
Linking a package results in showing that package in the repository's package list,
and shows a link to the repository on the package site (as well as a link to the repository issues).
## Access Restrictions
| Package owner type | User | Organization |
|--------------------|------|--------------|
2023-01-16 22:24:24 +00:00
| **read** access | public, if user is public too; otherwise for this user only | public, if org is public, otherwise for org members only |
2022-04-01 15:31:40 +00:00
| **write** access | owner only | org members with admin or write access to the org |
N.B.: These access restrictions are [subject to change ](https://github.com/go-gitea/gitea/issues/19270 ), where more finegrained control will be added via a dedicated organization team permission.
## Create or upload a package
Depending on the type of package, use the respective package-manager for that. Check out the sub-page of a specific package manager for instructions.
2022-03-30 08:42:47 +00:00
## View packages
You can view the packages of a repository on the repository page.
1. Go to the repository.
1. Go to **Packages** in the navigation bar.
To view more details about a package, select the name of the package.
## Download a package
To download a package from your repository:
1. Go to **Packages** in the navigation bar.
1. Select the name of the package to view the details.
1. In the **Assets** section, select the name of the package file you want to download.
## Delete a package
2023-01-16 22:24:24 +00:00
You cannot edit a package after you have published it in the Package Registry. Instead, you
2022-03-30 08:42:47 +00:00
must delete and recreate it.
To delete a package from your repository:
1. Go to **Packages** in the navigation bar.
1. Select the name of the package to view the details.
1. Click **Delete package** to permanently delete the package.
## Disable the Package Registry
The Package Registry is automatically enabled. To disable it for a single repository:
1. Go to **Settings** in the navigation bar.
1. Disable **Enable Repository Packages Registry** .
Previously published packages are not deleted by disabling the Package Registry.
