iojs.org
iojs.org copied to clipboard
latest / semver alias URL for the latest version's tarball
would be nice to be able to do something like GET http://iojs.org/download/latest/iojs-latest.tar.gz and maybe a semver version like ~1.0.2
You mean as a header?
no, a 303 redirect or just another API end point. so i can curl latest without knowing the actual latest version.
+1 to having a single endpoint pointing to the latest build, though this may need to be brought to the build team
@jonathanong couldn't you use http://semver.io/?
» curl https://semver.io/iojs.json | json
{
"stable": "1.0.3",
"unstable": "1.0.3",
"all": [
"1.0.0",
"1.0.1",
"1.0.2",
"1.0.3"
],
"stableVersions": [
"1.0.0",
"1.0.1",
"1.0.2",
"1.0.3"
],
"updated": "2015-01-22T20:21:32.953Z"
}
» curl https://semver.io/iojs/stable
1.0.3
i want to do this, which i can do with node but not iojs:
curl http://nodejs.org/dist/node-latest.tar.gz | tar -C /usr/local --strip-components=1 -xvz
That prints a list of files?
that installs node...
OH
I see what you mean.
@rvagg can we have http://iojs.org/download/latest/iojs-latest.tar.gz point to the latest stable? We could also do a nightly one.
@jonathanong how do you propose semver selectors would look like / work for this?
http://iojs.org/download/~1.0.0/iojs.tar.gz? whatever makes sense, but i'd expect the semver to be within //s for easier routing.
I'm not convinced this is a good idea just to avoid an additional lookup. You're essentially asking for a symlink copy for each file in each version directory too because we have one per supported platform.
I think it would be better to not symlink but have ngnix serve the correct one.
Basically, since nodejs.org does this, should we also?
what nodejs.org serves is the source tarball, does it serve an installable tarball for each platform?
I do know it installed properly for me. (OS X)
+1 to some kind of easy-to-get-to latest tarball url, at least for the source code tarball (and/or xzball).