replace source view / handler with redirect to crates.io source view

[syphar]

IMO with the new crates.io source browser, we don't need our (super old) source browser any more.
Of course we'll keep the rustdoc source browsers. storage-features that were only there for the source browser can go too.

Happy to discuss, not sure if I forget use-cases that crates.io doesn't support?

• SEO / crawling?
• binary file download from the archive (I'm actually fine with removing this, for security)

I spent some time to build it in a way that old URLs to specific files are properly redirected to the corresponding crates.io source file.

Source archives stay for now, we use them to fetch readme's later. I might switch that to fetching them from crates.io too, let's see.

When this is deployed and works fine, we can stop storing the source file list in releases.files and drop the column. This will save us some storage and give us some performance.

[GuillaumeGomez]

crates.io source view doesn't work without JS unlike docs.rs. Not sure if important or not though...

[syphar]

crates.io source view doesn't work without JS unlike docs.rs. Not sure if important or not though...

oh yeah, valid point. Do you have a tendency?

Non-JS People won't even reach the source view through the menu, only way is probably through search results somehow.

[GuillaumeGomez]

Someone mentioned on the crates.io zulip thread that it was an issue for them.

[syphar]

Someone mentioned on the crates.io zulip thread that it was an issue for them.

I'm wondering:

• if there are enough no-js users to justify a third code browser, and
• if the non-js users would be fine with the rustdoc source view, which seems to work without js too?

[GuillaumeGomez]

if there are enough no-js users to justify a third code browser, and

I'd say no. But considering we had a meeting about rust websites coherency, I would have expected such discussions to happen before crates.io team decided to do it on their own with an inferior version in pretty much all regards, leaving the debate for us to decide if it's worth keeping these pages or just remove them and leave them to crates.io's.

if the non-js users would be fine with the rustdoc source view, which seems to work without js too?

The rustdoc output is incomplete, it doesn't list all files in the published crate, so the end goal is different.

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.