https://github.com/w4/chartered

✈️ a private, authenticated, permissioned cargo registry
https://github.com/w4/chartered

Last synced: 3 months ago
JSON representation

✈️ a private, authenticated, permissioned cargo registry

• Host: GitHub
• URL: https://github.com/w4/chartered
• Owner: w4
• License: wtfpl
• Created: 2021-08-27T21:16:34.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2022-10-22T14:22:18.000Z (over 2 years ago)
• Last Synced: 2024-10-23T06:07:39.443Z (3 months ago)
• Language: Rust
• Homepage:
• Size: 2.18 MB
• Stars: 128
• Watchers: 3
• Forks: 9
• Open Issues: 14
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-rust - w4/chartered - A private, authenticated, permissioned Cargo registry [](https://github.com/w4/chartered/actions/workflows/ci.yml) (Registries / Web programming)
• awesome-rust-cn - w4/chartered - (注册表 Registries / 网络编程 Web programming)

README

        
# chartered

a little dig at creating a private cargo repository with authenticated downloads, the plan is to have cargo connect to

a git server we setup that can serve a fake index generated just for the authenticated user that we can embed temporary

authentication credentials into.

learn more at https://book.chart.rs/

designed to be easily morphable into a first-class authenticated registry-provider once [one][1] [of][2] the cargo RFCs go

through.

[1]: https://github.com/rust-lang/rfcs/pull/2719

[2]: https://github.com/rust-lang/rfcs/pull/3139

[open tasks](https://github.com/w4/chartered/issues)

#### fine grained permissions per user per crate

- VISIBLE

- PUBLISH_VERSION

- YANK_VERSION

- MANAGE_USERS

#### organisation support

crates are required to be under an organisation, the organisation can be specified when declaring the custom registry

in `.cargo/config.toml` like so:

```

[registries]

my-org       = { index = "ssh://chart.rs:22/my-org" }

my-other-org = { index = "ssh://chart.rs:22/my-other-org" }

```

#### screen shots