ipfs
Add a way to link to the latest version directly
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
Maybe use js trickery to update visible, clickable links on the website.
So there would be file current which will contain version number of the most recently released full version. Then on website link: go-ipfs_current_linux-386.tar.gz which will work but when someone has js enabled (90% of cases) it will be rewritten to go-ipfs_$(cat current)_linux-386.tar.gz (I am using shell syntax but it would be done in js).
If someone has no js enabled he will be left with go-ipfs_current_linux-386.tar.gz which should also work.
Other solutions would require changes to the protocol and it might be quite useful feature, to be able create redirect links, but I don't think it should be focus now.
