Template
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo synced 2024-12-13 06:51:57 +01:00
forgejo/docs/content/usage/packages/overview.en-us.md
John Olheiser bd4c7ce578
Docusaurus-ify (#26051)
This PR cleans up the docs in a way to make them simpler to ingest by
our [docs repo](https://gitea.com/gitea/gitea-docusaurus).

1. It includes all of the sed invocations our ingestion did, removing
the need to do it at build time.
2. It replaces the shortcode variable replacement method with
`@variable@` style, simply for easier sed invocations when required.
3. It removes unused files and moves the docs up a level as cleanup.

---------

Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-07-26 04:53:13 +00:00

4.1 KiB

date title slug sidebar_position draft toc menu
2021-07-20T00:00:00+00:00 Package Registry overview 1 false false
sidebar
parent name sidebar_position identifier
packages Overview 1 packages-overview

Package Registry

Starting with Gitea 1.17, the Package Registry can be used as a public or private registry for common package managers.

Supported package managers

The following package managers are currently supported:

Name Language Package client
Alpine - apk
Cargo Rust cargo
Chef - knife
Composer PHP composer
Conan C++ conan
Conda - conda
Container - any OCI compliant client
CRAN R -
Debian - apt
Generic - any HTTP client
Go Go go
Helm - any HTTP client, cm-push
Maven Java mvn, gradle
npm JavaScript npm, yarn, pnpm
NuGet .NET nuget
Pub Dart dart, flutter
PyPI Python pip, twine
RPM - yum, dnf, zypper
RubyGems Ruby gem, Bundler
Swift Swift swift
Vagrant - vagrant

The following paragraphs only apply if Packages are not globally disabled!

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
read access public, if user is public too; otherwise for this user only public, if org is public, otherwise for org members only
write access owner only org members with admin or write access to the org

N.B.: These access restrictions are subject to change, 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.

View packages

You can view the packages of a repository on the repository page.

  1. Go to the repository.
  2. 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.
  2. Select the name of the package to view the details.
  3. In the Assets section, select the name of the package file you want to download.

Delete a package

You cannot edit a package after you have published it in the Package Registry. Instead, you must delete and recreate it.

To delete a package from your repository:

  1. Go to Packages in the navigation bar.
  2. Select the name of the package to view the details.
  3. 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.
  2. Disable Enable Repository Packages Registry.

Previously published packages are not deleted by disabling the Package Registry.