Official support for https://install.meteor.com?release=$METEOR_VERSION

1

Is the release=$METEOR_VERSION query string officially supported for installing a particular version of Meteor in a hosting environment, rather than only the latest recommended version?

It doesn’t seem to be documented anywhere, but I had found out about the release=$METEOR_VERSION query string option simply by trying it back in March 2016 and it happened to work.

https://install.meteor.com/?release=1.3.4.1 works if I want to deploy with Meteor 1.3.4.1.

However I don’t think https://install.meteor.com/?release=1.4-beta.7 would work because the URL
https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.4-beta.7/meteor-bootstrap-os.linux.x86_64.tar.gz does not respond with the expected file download.

So downloading a previous recommended version using the query string happens to work fine. However the same query string approach may not work for a beta version.

It appears that the only way currently to install a beta version via deployment script is to install the latest recommended version the normal way then run meteor update.

Could support be added to make it possible to download a beta version using the release=$METEOR_VERSION query string? It would be a more elegant way than via a meteor update.

2

I’m sure support for this could be added, but I’m not sure MDG would want to. They want people to be able to try out beta releases (which meteor update --release provides), but I don’t think they’ll want to add the extra overhead necessary to “release” (publish to their CDN, etc.) beta builds. That being said, you might want to consider opening a feature request with MDG via the GH issues, to see what they say.