Alexandrie is an alternative crate registry suitable for use with Cargo.
This repository implements the Cargo APIs and interacts with a crate index as specified in the Cargo's Alternative Registries RFC.
This allows to have a private registry to host crates that are specific to what you're doing and not suitable for publication on crates.io while maintaining the same build experience as with crates from crates.io.
Alexandrie is built using Tide and offers multiple options to be used as its database.
To build, you can run
cargo build [--release].
Before running it, you need to configure your instance in the
The database is configured through the
[database] # Replace the '<...>' placeholders by their real actual values. # For MySQL url = "mysql://<user>:<password>@<hostname>:<port>/<database>" # For PostgreSQL url = "postgresql://<user>:<password>@<hostname>:<port>/<database>" # For SQLite url = "<path-to-sqlite-database-file>" # or: url = ":memory:" # ephemeral in-memory database, doesn't persists between restarts
Optionally, you can specify the maximum number of simultaneous open connections for the database connection pool:
max_conns = 1
If not specified, the
r2d2 default value is used.
Then, you can configure the crates' tarballs storage strategy and the crate index management strategy that you want to use.
Here is how to do it (these are also the defaults, you can leave them out if you want):
[index] type = "command-line" path = "crate-index" [storage] type = "disk" path = "crate-storage"
You can also configure things like the address and port of the server:
[general] addr = "127.0.0.1" port = 3000
Then, you need to configure a crate index.
A crate index is simply a git repository that the registry uses to keep metadata information about each crate and their individual versions.
The repository can be created on any machine you want, as long as it is reachable from the current machine as a git remote in a clone of that repository.
The remote can be specified using either an HTTPS or SSH link.
If you're using SSH for the remote link, Cargo might have an issue where it can't fetch from the registry's index when doing
cargo search or
This is because Cargo uses
libgit2 to fetch from remotes and fails to find the SSH credentials needed to do so.
To work around this issue, you may need to set the
CARGO_NET_GIT_FETCH_WITH_CLI environment variable to
true, so that Cargo will offload the fetching from remotes operation to the
git command-line utility.
See issue #44 for a previous occurence of this exact issue.
To run the registry, be sure to clone your crate index at the location designated by the
path key in
The default for it is
To clone an existing crate index, you can run:
# Replace the '<...>' placeholders by their real actual values. git clone <url-of-the-crate-index> <path-from-config> # <url-of-the-crate-index>: URL to the git repository serving as the registry's crate index. # <path-from-config>: Path to the same directory as the one specified as `index.path` in the `alexandrie.toml`. # Example: git clone 'https://github.com/Hirevo/alexandrie-index' 'crate-index'
If you want to create one, you can refer to the Cargo's Alternative Registries RFC to learn about the layout of such an index.
You can also visit the crates.io index or the crates.polomack.eu index as deployed examples.
Once everything is configured, you can run with:
cargo run [--release].
Then, if you want to use this index with Cargo, you can follow these steps:
~/.cargo/configfile, and add the following code:
# Replace the '<...>' placeholders by their real actual values. [registries.<name-of-your-registry>] index = "<url-of-the-crate-index>" # <name-of-your-registry>: A name of your choosing, that you'll be using to refer to it in `cargo` commands. # <url-of-the-crate-index>: URL to the git repository serving as the registry's crate index. # BE CAREFUL: this is not the URL to the registry's API or frontend.
cargo login --registry <name-of-your-registry>and enter your author token.
cargo [search|publish] --registry <name-of-your-registry>
If you wish to have a more concrete resource to learn how to setup an Alexandrie instance, like a shell script, you may refer to an example installation script which can help you get started:
To get started, you'll need to copy the
example.env file and save it as
.env (filename is important). You should:
APPDATAto the path of a new directory where the container will store the crate index, crate files, & database file.
CRATE_INDEXto the SSH path of an existing repo with a valid index
GIT_EMAILto valid git values that will be used when Alexandrie commits & pushes those commits to the index.
GIT_SSH_KEYto a new or existing passwordless SSH key. The
.pubkey associated with this key should be added to GitHub/GitLab/etc. to grant access to push to the crate index.
These items will be mounted into the Docker container, and need to be accessible by a user with UID and GID
1000. If Docker appears to complain that any of these are inaccessible, check your paths and your file/directory permissions.
By default, Alexandrie will use SQLite for its database. If you want to use either MySQL or PostgreSQL instead, you'll need to create a
docker/<database>/. The entire contents of this file will be copied and used as the password for the root user of the database; don't add an ending newline unless your password actually contains one!
To run Alexandrie, call the
run_docker.sh script, with arguments depending on the action and database you want. For example, to start Alexandrie in the background with the default SQLite database, do:
To stop Alexandrie, do:
The script assumes a Bash environment, and was only tested on Ubuntu 19.10. For more details and examples, see the docs.
➜ ~ ./alexandrie -V alexandrie version:0.3.14 branch:master commit-hash:9560be54 build_time:2020-08-25 02:39:21 build_env:rustc 1.45.0 (5c1f21c3b 2020-07-13),stable-x86_64-apple-darwin (default) ➜ ~
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.