forked from gitea/gitea
1
0
Fork 0
gitea/routers/api/packages
merlleu a587d25261
Add auth-required to config.json for Cargo http registry (#26729)
Cargo registry-auth feature requires config.json to have a property
auth-required set to true in order to send token to all registry
requests.
This is ok for git index because you can manually edit the config.json
file to add the auth-required, but when using sparse
(setting index url to
"sparse+https://git.example.com/api/packages/{owner}/cargo/"), the
config.json is dynamically rendered, and does not reflect changes to the
config.json file in the repo.

I see two approaches:
- Serve the real config.json file when fetching the config.json on the
cargo service.
- Automatically detect if the registry requires authorization. (This is
what I implemented in this PR).

What the PR does:
- When a cargo index repository is created, on the config.json, set
auth-required to wether or not the repository is private.
- When the cargo/config.json endpoint is called, set auth-required to
wether or not the request was authorized using an API token.
2023-08-28 07:05:39 +00:00
..
alpine Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
cargo Add auth-required to config.json for Cargo http registry (#26729) 2023-08-28 07:05:39 +00:00
chef Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
composer Remove `db.DefaultContext` in `routers/` and `cmd/` (#26076) 2023-07-23 23:47:27 -04:00
conan Remove `db.DefaultContext` in `routers/` and `cmd/` (#26076) 2023-07-23 23:47:27 -04:00
conda Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
container Remove `db.DefaultContext` in `routers/` and `cmd/` (#26076) 2023-07-23 23:47:27 -04:00
cran Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
debian Fix handling of Debian files with trailing slash (#26087) 2023-07-24 16:19:44 +02:00
generic Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
goproxy Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
helm Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
helper Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
maven Add support for different Maven POM encoding (#25873) 2023-07-14 09:39:15 +00:00
npm Remove `db.DefaultContext` in `routers/` and `cmd/` (#26076) 2023-07-23 23:47:27 -04:00
nuget Fix NuGet search endpoints (#25613) 2023-08-14 02:50:55 +00:00
pub Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
pypi Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
rpm Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
rubygems Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
swift Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
vagrant Replace `interface{}` with `any` (#25686) 2023-07-04 18:36:08 +00:00
README.md Add package registry architecture overview (#23445) 2023-03-13 18:15:09 -04:00
api.go Remove redundant "RouteMethods" method (#26024) 2023-07-21 00:43:49 +02:00

README.md

Gitea Package Registry

This document gives a brief overview how the package registry is organized in code.

Structure

The package registry code is divided into multiple modules to split the functionality and make code reuse possible.

Module Description
models/packages Common methods and models used by all registry types
models/packages/<type> Methods used by specific registry type. There should be no need to use type specific models.
modules/packages Common methods and types used by multiple registry types
modules/packages/<type> Registry type specific methods and types (e.g. metadata extraction of package files)
routers/api/packages Route definitions for all registry types
routers/api/packages/<type> Route implementation for a specific registry type
services/packages Helper methods used by registry types to handle common tasks like package creation and deletion in routers
services/packages/<type> Registry type specific methods used by routers and services

Models

Every package registry implementation uses the same underlaying models:

Model Description
Package The root of a package providing values fixed for every version (e.g. the package name)
PackageVersion A version of a package containing metadata (e.g. the package description)
PackageFile A file of a package describing its content (e.g. file name)
PackageBlob The content of a file (may be shared by multiple files)
PackageProperty Additional properties attached to Package, PackageVersion or PackageFile (e.g. used if metadata is needed for routing)

The following diagram shows the relationship between the models:

Package <1---*> PackageVersion <1---*> PackageFile <*---1> PackageBlob

Adding a new package registry type

Before adding a new package registry type have a look at the existing implementation to get an impression of how it could work. Most registry types offer endpoints to retrieve the metadata, upload and download package files. The upload endpoint is often the heavy part because it must validate the uploaded blob, extract metadata and create the models. The methods to validate and extract the metadata should be added in the modules/packages/<type> package. If the upload is valid the methods in services/packages allow to store the upload and create the corresponding models. It depends if the registry type allows multiple files per package version which method should be called:

  • CreatePackageAndAddFile: error if package version already exists
  • CreatePackageOrAddFileToExisting: error if file already exists
  • AddFileToExistingPackage: error if package version does not exist or file already exists

services/packages also contains helper methods to download a file or to remove a package version. There are no helper methods for metadata endpoints because they are very type specific.