Install script fetches 404 html instead of tarball

[ellemenno]

Following the install directions, I'm getting this error:

tar: Unrecognized archive format

If I'm not horribly confused, it's because the install script references

http://rvm-fw.herokuapp.com/rubies/packages/rvm/${stable_version}.tar.gz

which fetches stable-version.txt to evaluate into

http://rvm-fw.herokuapp.com/rubies/packages/rvm/1.18.14.tar.gz

which does not resolve to a tarball but rather the message that your ruby is in another castle:

You've dug in the wrong spot - there are no rubies here Keep digging though! The treasure has to be somewhere!

confusingly, the rubies page links to

http://rvm-fw.herokuapp.com/rubies/packages/rvm/rvm-1.18.14.tar.gz (note the rvm- prefix)

but this url returns the same 404.

[stevenhaddox]

@ellemenno RVM::FW isn't meant to be run from Heroku. You need to clone it locally and then run the rake task to download all the rubies you want it to serve. Once that's done you'd tarball / zip it up and copy the codebase along with the binaries to your internal server. You'd start the Sinatra application (which is what's deployed to Heroku) and be able to install RVM from any machine that can access that Sinatra app.

I don't include the binaries as they change fairly frequently and the git repo gets huge insanely fast (I did at one point, but it was a nightmare to maintain). The Heroku instance is mainly meant to demonstrate what it will look like once it's deployed successfully, but not actually host the binaries. It just shows that usage for a user of your RVM::FW instance is much easier than setup itself is. If you can reach RVM::FW on Heroku you can probably just download RVM directly and use it most likely ;)

Please let me know if you need help with any of the setup instructions.