cargo
Here are 541 public repositories matching this topic...
-
Updated
Jul 17, 2021 - Rust
-
Updated
Jul 12, 2021 - Rust
-
Updated
May 28, 2021 - Rust
-
Updated
Jul 10, 2021 - Rust
-
Updated
May 8, 2021 - Rust
-
Updated
Jul 17, 2021 - Rust
-
Updated
Sep 7, 2020 - Python
-
Updated
Jul 17, 2021 - Rust
-
Updated
Jun 9, 2021 - Rust
-
Updated
Jul 13, 2021 - Rust
-
Updated
Oct 13, 2017 - HTML
-
Updated
Jun 28, 2021 - Rust
-
Updated
May 21, 2021 - Rust
-
Updated
Feb 13, 2021 - Rust
pre-compiled binary
Hi.
I would love to see cargo-chef had pre-compiled binary on the release page.
I tend to avoid invoking the cargo install command in CI workflow and downloading the pre-compiled binary directly.
Resulting in just ~14 minutes, compared to ~30 minutes.
So instead of cargo install trunk, I do:
# install trunk
wget -qO- https://github.com/thedodd/trunk/releases/doThis is a tracking issue for additional Store implementations.
Here is a non-exhaustive list of potential candidates for an Store implementation:
- S3Storage:
This would store crate tarballs and rendered README pages into Amazon's S3. - RemoteStorage:
Requires to implement a companion server.
The idea is to have a reserved folder on another machine which runs a comp
-
Updated
Jul 1, 2021 - TypeScript
Improve this page
Add a description, image, and links to the cargo topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the cargo topic, visit your repo's landing page and select "manage topics."
In the docs, there are several cases such as here where code snippet examples are shown side by side, without actually specifying which files they are (eg. deny.toml vs Cargo.toml) which can lead to confusion for users. Every code snippet should just specify
# <name>.tomlat the top for clarity.