bd4c7ce578
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>
3.1 KiB
| date | title | slug | sidebar_position | draft | toc | menu | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2022-11-20T00:00:00+00:00 | Cargo Package Registry | cargo | 5 | false | false |
|
Cargo Package Registry
Publish Cargo packages for your user or organization.
Requirements
To work with the Cargo package registry, you need Rust and Cargo.
Cargo stores information about the available packages in a package index stored in a git repository. This repository is needed to work with the registry. The following section describes how to create it.
Index Repository
Cargo stores information about the available packages in a package index stored in a git repository.
In Gitea this repository has the special name _cargo-index.
After a package was uploaded, its metadata is automatically written to the index.
The content of this repository should not be manually modified.
The user or organization package settings page allows to create the index repository along with the configuration file. If needed this action will rewrite the configuration file. This can be useful if for example the Gitea instance domain was changed.
If the case arises where the packages stored in Gitea and the information in the index repository are out of sync, the settings page allows to rebuild the index repository. This action iterates all packages in the registry and writes their information to the index. If there are lot of packages this process may take some time.
Configuring the package registry
To register the package registry the Cargo configuration must be updated.
Add the following text to the configuration file located in the current users home directory (for example ~/.cargo/config.toml):
[registry]
default = "gitea"
[registries.gitea]
index = "https://gitea.example.com/{owner}/_cargo-index.git"
[net]
git-fetch-with-cli = true
| Parameter | Description |
|---|---|
owner |
The owner of the package. |
If the registry is private or you want to publish new packages, you have to configure your credentials.
Add the credentials section to the credentials file located in the current users home directory (for example ~/.cargo/credentials.toml):
[registries.gitea]
token = "Bearer {token}"
| Parameter | Description |
|---|---|
token |
Your personal access token |
Publish a package
Publish a package by running the following command in your project:
cargo publish
You cannot publish a package if a package of the same name and version already exists. You must delete the existing package first.
Install a package
To install a package from the package registry, execute the following command:
cargo add {package_name}
| Parameter | Description |
|---|---|
package_name |
The package name. |
Supported commands
cargo publish
cargo add
cargo install
cargo yank
cargo unyank
cargo search