how to use private git repository in cargo with gitlab crates-index about alexandrie HOT 8 CLOSED

Your config.json file (living at the root of your crate index) should be of the following shape:

{
    "dl": "<link-to-your-instance-of-alexandrie>/api/v1/crates/{crate}/{version}/download",
    "api": "<link-to-your-instance-of-alexandrie>",
    "allowed-registries": [
        "https://github.com/rust-lang/crates.io-index",
        "<link-to-your-index-repository>"
    ]
}

where you should replace:

• <link-to-your-instance-of-alexandrie>:
  This is the link to your live instance of Alexandrie.
  Using concrete examples:
  • for crates.io, this value is: https://crates.io.
  • for crates.polomack.eu (my own registry), this value is: https://crates.polomack.eu.
• <link-to-your-index-repository>:
  This is the link to your crate index repository (the exact repository where this config.json file is living into).
  Using concrete examples:
  • for crates.io, this value is: https://github.com/rust-lang/crates.io-index.
  • for crates.polomack.eu, this value is: https://github.com/Hirevo/alexandrie-index.

Is that helpful ?
Also, have you managed to have an Alexandrie instance built and running, or have you encountered an issue on that front ?

from alexandrie.

You need to put the URL to the git repo into .cargo/config and the config.json within that repo must contain the correct URLs to alexandrie. Everything just worked for me afterwards.

from alexandrie.

Yeah, at first sight on the error output, I would suspect the cause of the error to be within the config.json file in your crate index.
Maybe it isn't pointing to the right endpoint.

from alexandrie.

gitlab can do file storg ? not use database.

from alexandrie.

A database is currently a requirement to have in Alexandrie, to serve as the source of truth in case of conflicts between the crate index and the crate storage (if they become out of sync) and/or for faster lookup of crate records.
If you want the least bothersome database option to setup, you can use the SQLite one, which is basically using a single file as your database.

The crate index is just expected to be a Git repository, so it can totally be hosted in GitLab without issues.

In the other hand, for the crate storage, we don't currently allow storing actual crate archives (the actual code of the crates) in a Git repository, because all of these archives can become quite large as a whole and I don't really see the benefit of versioning the crate storage (because the crate index, which is first consulted to lookup these archives, is already versioned).

from alexandrie.

I'd like to be able to store crystals in a simple, lightweight way, but There was a problem with the configuration of that I'm here now config.json.I don't know how to solve it

from alexandrie.

Your config.json file (living at the root of your crate index) should be of the following shape:

{
    "dl": "<link-to-your-instance-of-alexandrie>/api/v1/crates/{crate}/{version}/download",
    "api": "<link-to-your-instance-of-alexandrie>",
    "allowed-registries": [
        "https://github.com/rust-lang/crates.io-index",
        "<link-to-your-index-repository>"
    ]
}

where you should replace:

• <link-to-your-instance-of-alexandrie>:
  This is the link to your live instance of Alexandrie.
  Using concrete examples:

  • for crates.io, this value is: https://crates.io.
  • for crates.polomack.eu (my own registry), this value is: https://crates.polomack.eu.

• <link-to-your-index-repository>:
  This is the link to your crate index repository (the exact repository where this config.json file is living into).
  Using concrete examples:

  • for crates.io, this value is: https://github.com/rust-lang/crates.io-index.
  • for crates.polomack.eu, this value is: https://github.com/Hirevo/alexandrie-index.

Is that helpful ?
Also, have you managed to have an Alexandrie instance built and running, or have you encountered an issue on that front ?

Thanks to your help.
I just flow you step solved my problem.

But in the process, I found a few problems，related links are as follows

• When Cargo.toml version not changed,cargo publish error. Response 500,body message is empty
• Support LDAP login accout? Like artifactory ldap login. Not register custom personal accout

from alexandrie.

Thanks for filing these additional issues (and even coming up for a PR to address one of them).
Since the original problem of this particular issue seems solved, I am going to close it.
Feel free to reopen it if it isn't the case.

from alexandrie.