Basic fixes required before rails.bat and config_check.rb will work as expected after installing rails installer for windows (2.2).

[Warren Postma]

I installed the rails installer 2.2 on windows 10.

Three things bother me:

1. You get the choice to install git or not.  Seriously? Who doesn't already have git installed?   If you uncheck git, the contents of the config_check.rb need to be manually fixed to avoid having the config_check.rb script output bogus errors. My suggested fix is the following Config = {} section, from which I have removed all the File.join() and left only an unqualified git.exe, ssh-keygen.exe, and cat.exe, which must be assumed to be in the path, if the user unchecked the Git install option.  

2. After installation, the contents of the rails.bat file are bogus.

@ECHO OFF
IF NOT "%~f0" == "~f0" GOTO :WinNT
@"C:\Users\emachnic\GitRepos\railsinstaller-windows\stage\Ruby2.2.0\bin\ruby.exe" "C:/Users/emachnic/GitRepos/railsinstaller-windows/stage/Ruby2.2.0/bin/rails" %1 %2 %3 %4 %5 %6 %7 %8 %9
GOTO :EOF
:WinNT
@"C:\Users\emachnic\GitRepos\railsinstaller-windows\stage\Ruby2.2.0\bin\ruby.exe" "%~dpn0" %*

My user name is not emachnic.  And the above is archaic in the extreme. Is anybody running ruby 2.0 on MS DOS or Windows 98?  The batch file could probably be skipping the "NT 3.5 or later" check in 2016....

@ECHO OFF
"c:\RailsInstaller\Ruby2.2.0\bin\ruby.exe" "c:/RailsInstaller/Ruby2.2.0/bin/rails" %*

With those two changes above, I get an actual working system. A windows user who clicks next-next and didn't even customize anything isn't going to get a working "rails.bat" and therefore, their entire "installation" will not work.

Warren

[Warren Postma]

This was reported in MARCH (earlier thread) and still NOTHING is done?

Is this project maintained?

W

[Warren Postma]

Github issue is here:

https://github.com/railsinstaller/railsinstaller-windows/issues/81

This project appears unmaintained at this point, I will do what I can to help out.   Rails on Windows appears to be suffering from an OOBE fail.

Simplest workaround, from a command prompt, after install run:

run gem update --system && gem update --no-document