-
Notifications
You must be signed in to change notification settings - Fork 49
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
No config.json #128
Comments
This might be an inconsistency in the mirror. Whereabouts is the config.json supposed to be located - in the root of the git repo, or as part of what HTTP serves? The former I have accounted for, but if the latter, I might not actually know about its existence. |
It is supposed to be located at the root of the index, when downloading
using http/https, as described here:
https://doc.rust-lang.org/cargo/reference/registry-index.html
Basically I expect a similar type of reply from Panamax as I get from
crates.io when I do:
hpenne$ curl https://index.crates.io/config.json
{
"dl": "https://static.crates.io/crates",
"api": "https://crates.io"
}
I'm scripting something that needs to resolve the URL of the API, and
that is specified by the contents of this json file.
Best regards,
Helge Penne
…On Thu, 21 Mar 2024 at 18:09, Keith ***@***.***> wrote:
This might be an inconsistency in the mirror. Whereabouts is the
config.json supposed to be located - in the root of the git repo, or as
part of what HTTP serves? The former I have accounted for, but if the
latter, I might not actually know about its existence.
—
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECO7YUOMCQ25YTGBJNI3NLYZMH5TAVCNFSM6AAAAABE7KZZLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJTGA3DIMRWGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I did something similar to #120 on my local network. Out of the box, without configuring cargo for panamax, cargo fails to fetch https://index.crates.io/config.json It seems to work with "index" in the url but thats not what cargo is fetching by default. I think that if panamax returns config.json in the url above, then no client configuration is required, as in no need to edit .cargo/config. |
We have a Panamax mirror at work, but it does not seem to serve up the expected config.json file at the root. I've tried to fetch it with curl, but get nothing. I need this for some automated tools that need to find the API URL through the config.json.
We have another Artifactory-based mirror, and that returns the config.json as expected.
Any idea what could be wrong?
The text was updated successfully, but these errors were encountered: