Skip to content

link manifests.txt #1047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marcoieni merged 1 commit into from
May 13, 2026
Merged

link manifests.txt #1047

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions src/infra/channel-layout.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,15 @@ A lot of the content herein is derived from


Rust releases are deployed onto `static.rust-lang.org` where they are served via
`https`. There are several parts to a release channel (`stable`, `beta`,
`nightly`) but they all key off a manifest file and then go from there.
`https` through our [CDNs](./docs/cdn.md).
There are several parts to a release channel (`stable`, `beta`, `nightly`)
but they all key off a manifest file and then go from there.

## Channel manifests

The [`manifests.txt`](https://static.rust-lang.org/manifests.txt) file lists
the paths of the channel manifest that have been published so far.

There is a top level directory `/dist/` which contains the channel manifests.
The manifests are named `channel-rust-[channelname].toml`. Each channel manifest
is accompanied by a `.sha256` file which is a checksum of the manifest file and
Expand Down Expand Up @@ -129,4 +133,3 @@ Since components and extensions are target-specific in the `pkg` tables, you
will be able to see that `rust-std` for every target is specified in every
`rust` target's extensions. This allows for cross-compilation by installation of
any `rust-std` on any build system.

7 changes: 5 additions & 2 deletions src/infra/docs/cdn.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@
Users of the Rust programming language interact with the infrastructure of the
project in various different ways. They access the project's website and
documentation, query the crates index, and download Rust releases and crates.
These resources are hosted by the Rust project and served through a [Content
Delivery Network] (CDN).
These resources are hosted by the Rust project and served through a
[Content Delivery Network] (CDN).

This document outlines why we use CDNs, for what, and how we have set them up.

Expand Down Expand Up @@ -63,6 +63,8 @@ pipeline, which is why this distribution has by far the highest traffic volume.

Rust binaries are static and are stored in [Amazon S3], from where they are
served by the CDNs.
The supported public layout for release channel manifests
is documented in the [release channel layout][release-channel-layout].

The distribution for `static.rust-lang.org` has a custom router that runs in a
[AWS Lambda] function. The router provides a way to list files for a release and
Expand All @@ -85,4 +87,5 @@ distribution.
[aws lambda]: https://aws.amazon.com/lambda/
[content delivery network]: https://en.wikipedia.org/wiki/Content_delivery_network
[fastly]: https://www.fastly.com/
[release-channel-layout]: ../channel-layout.md
[rust-lang/simpleinfra]: https://github.com/rust-lang/simpleinfra
Loading