-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows RailsInstaller for Rails 4.2 and Ruby 2.2 still broken? #81
Comments
Hi, |
Just change the paths in those files to the correct path. Going by the pattern, a simple replace all by a text editor that can see the entire tree (e.g. Sublime, Atom, most IDEs) should be able to solve most of these issues. This has been reported (and closed) already: #73 There are a lot of path mistakes in RailsInstaller though. I agree that this should be fixed in later versions. |
Thanks very much. It worked. |
Just to make it clear - the files to edit are all gem BAT files in It is advisable to change the Do not tamper with |
Hi, |
It's ridiculous that bug is still there... (hard coded paths to the developer's machine...???) Give me back my 20 minutes! |
Thanks margaretcsmith. "gem install rails" solved my installation issue. |
After successful installation of Railsinstaller, open the bundled version of command-prompt and simply run |
How can I contribute and get the out of box installation experience fixed? Some developer who knows, please tell me. This is silly that it's been broken from March (see google groups) to October of 2016. That's 8 months. I'm new to ruby but I know a bad batch file when I see one. Maybe the MR should be "run gem update --system" and "gem update --no-document" when the install completes, and maybe the MR should be to drop these broken and outdated ruby binaries from ruby installer and actually just have the ruby installer do "gem install rails" |
My issues in installing rails got resolved using the guide on this website. |
alternatively, simply run the following to have the latest versions of all installed gems:
|
@ashmaroli thank you so much, "gem update --no-document" worked for me! |
Since rubygems v2.4.2, Windows binstubs for gem executables are generated with a hardcoded path to Ruby. This leads to the binstubs shipping with RailsInstaller-Windows being unusable, because they reference the Ruby path on the maintainer machine, rather than the machine that executed the installer (see railsinstaller#81). This is due to a fix in rubygems, which explicitely hardcodes the Ruby path in the binstubs, to work around a Bundler issue (see rubygems/rubygems#942). The author of the patch notes that it makes Ruby installations non-portable across machines - which is exacly the issue that we encounter there. The intended workaround for people needing portable installations is to re-generate the binstubs locally, by executing `gem pristine --all --executables-only`. This is how this PR implements the fix: it simply re-generates the binstubs with the correct path at the end of the installation. In the future, I may attempt to fix the issue upstream in rubygems, by allowing `--env-shebang` to generate a portable Ruby path again, as it was suggested in the original pull request.
The bug with the wrong paths in different batchfiles has not been corrected with Railsinstaller-3.3.0.exe First step was: install until the "Completing the RailsInstaller Setup Wizard" was shown. Don't click on "Finish" yet. Do what @margaretcsmith commented on 25 Jun 2016. After that I changed config_check.rb (located on C:\RailsInstaller\scripts) line 78 and line 82, because they referred to a wrong railsinstaller_path (2.0.0 instead of Ruby2.3.0") Then I clicked on "Finish" on the RailsInstaller-Setup with activated "Configure git and ssh when installation has completed." And... it worked 👍 |
Please try with the latest version. |
I just downloaded and tried RailsInstaller for Rails 4.2 and Ruby 2.2 from installRails.com. Things appear to install correctly but the paths to the executables are still apparently corrupt. No changes were made to the Windows PATH configuration, and so nothing works the way it should. Can't run ruby, rails, or git, to name the top three. (Well, not completely true. I can run Ruby if I manually go to C:\RailsInstaller\Ruby2.2.0\bin). When I look at paths in some batch files, I see things like: "C:\Users\emachnic\GitRepos..." as if hard-coded paths were randomly left in place by the developer. At least 2 months have passed since a bunch of threads were posted about problems like this and apparently still no fixes. Quite a disappointment and not a good way to convert a developer to Rails as a viable platform.
The text was updated successfully, but these errors were encountered: