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>.toml at the top for clarity.

Hi,

loving this project, thanks a lot!

Seems that there is an issue with the files copy/paste function. The overwrite option ("po" Keymap line 117) gets ignored and the file/folder renamed (number gets appended). Or did I miss some configuration option?

Plus there is a little mistake in the example keymap.toml:
Must be copy_dirname instead of copy_dir (line 111) if I'm correct.

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/do

This 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