Add a way to link to the latest version directly
- Dominant language
- Less
- Stars
- 50
- Forks
- 30
- Avg merge
- 50m
- Merged PRs (30d)
- 1
Description
> There MUST NOT be a dependency to update this website when a new version is released. That's super cumbersome. The gobuilder links explicitly avoided this problem. This was not by accident, but by design.
>
> One easy way to do is is to add a release dir (to mirror the git branch name) that gets updated by the dist.ipfs.io repo release process. this can symlink the files directly like so:
>
> ls -l go-ipfs/release
> go-ipfs_release_linux-386.tar.gz -> ../v0.3.11/go-ipfs_v0.3.11_linux-386.tar.gz
> go-ipfs_release_linux-amd64.tar.gz -> ../v0.3.11/go-ipfs_v0.3.11_linux-amd64.tar.gz
> This has the unfortunate side-effect that the files will be downloaded as go-ipfs_release_linux-386.tar.gz instead of preserving a version. Not sure how to solve that yet. What we need is effectively something like a 302 redirect. I can imagine a way of importing symlinks into ipfs not as dag hardlinks but as dag symlinks that the gateway serves as 302 redirects.
Other ideas?
Ref https://github.com/ipfs/website/pull/98#discussion_r53580825
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.