Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

private registry hosting cratesio setup #305

Open
guzzijones opened this issue Apr 24, 2024 · 2 comments
Open

private registry hosting cratesio setup #305

guzzijones opened this issue Apr 24, 2024 · 2 comments

Comments

@guzzijones
Copy link

guzzijones commented Apr 24, 2024

For others who may want to use kellnr as a private repo hosting crates-io packages here are the settings:

# .cargo/config
[source.crates-io]
replace-with = "kellnr-cratesio"

[registries.kellnr-cratesio]
index = "sparse+https://mykellnr.instance.com/api/v1/crates/"

[source.kellnr-cratesio]
registry = "sparse+https://mykellnr.instancecom/api/v1/crates/"

the cratesio source needs to point at the crates endpoint instead of cratesio
`"sparse+https://mykellnr.instancecom/api/v1/cratesio/" will ALWAYS try to go to the internet.

This still doesn't solve the problem of missing README.md on many cargo packages.

@Christiaan676
Copy link
Contributor

As far as I can tell everything is documented here: https://kellnr.io/documentation#global-config.

Kellnr has two endpoints:
For the crates.io proxy: sparse+https://yourkellnrhostname/api/v1/cratesio/
For the private registry: sparse+https://yourkellnrhostname/api/v1/crates/

In your example your forwarding all the requests for crates.io to the private registry endpoint, that is not going to work.

@guzzijones
Copy link
Author

we are pulling crates from cratesio and pushing them into kellnr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants