bb25f85ce8
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>
2.6 KiB
| date | title | slug | weight | draft | toc | menu | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2022-12-28T00:00:00+00:00 | Conda Packages Repository | conda | 25 | false | false |
|
Conda Packages Repository
Publish Conda packages for your user or organization.
Table of Contents
{{< toc >}}
Requirements
To work with the Conda package registry, you need to use conda.
Configuring the package registry
To register the package registry and provide credentials, edit your .condarc file:
channel_alias: https://gitea.example.com/api/packages/{owner}/conda
channels:
- https://gitea.example.com/api/packages/{owner}/conda
default_channels:
- https://gitea.example.com/api/packages/{owner}/conda
| Placeholder | Description |
|---|---|
owner |
The owner of the package. |
See the official documentation for explanations of the individual settings.
If you need to provide credentials, you may embed them as part of the channel url (https://user:password@gitea.example.com/...).
Publish a package
To publish a package, perform a HTTP PUT operation with the package content in the request body.
PUT https://gitea.example.com/api/packages/{owner}/conda/{channel}/{filename}
| Placeholder | Description |
|---|---|
owner |
The owner of the package. |
channel |
The channel of the package. (optional) |
filename |
The name of the file. |
Example request using HTTP Basic authentication:
curl --user your_username:your_password_or_token \
--upload-file path/to/package-1.0.conda \
https://gitea.example.com/api/packages/testuser/conda/package-1.0.conda
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 one of the following commands:
conda install {package_name}
conda install {package_name}={package_version}
conda install -c {channel} {package_name}
| Parameter | Description |
|---|---|
package_name |
The package name. |
package_version |
The package version. |
channel |
The channel of the package. (optional) |