I posted a question on the pik mailing list asking how I could solve this issue, but as of yet, I have received no reply.īack in my Rails project directory I ran my tests again (using Ruby 1.9.3) and they completed within 20 seconds. This was a bit of a clunky solution, but it worked and for that I was grateful. So, I reverted gem_home to its original value for both Ruby versions, switched to Ruby 1.9.3 and installed Rails a second time. Pik config gem_home =C:/ruby192/lib/ruby/gems/1.9.1įollowing this, my Ruby 1.9.3 version recognized all of the gems installed under 1.9.2 and although I could run scripts which required other gems (FXRuby for example), annoyingly I still got the same error message when I tried to start the rails server. No problemo, I had already installed 1.9.2 using the mighty RubyInstaller.Īfter that, as you can install pik via rubygems, it’s a matter of opening a command prompt and typing: In order to install pik you need a working version of Ruby. Pik bills itself as a tool to manage multiple versions of Ruby on Windows which can be used from the Windows command line (cmd.exe), Windows PowerShell, or Git Bash. Hmmm… I wanted to keep Ruby 1.9.2 installed, but needed a way to speed things up, so I started looking for ways to manage multiple Ruby versions on Windows (yes, I know, Windoof, but just remember that you cannot play Skyrim on Linux without performing a backwards somersault through your own sphincter). I read through a couple of questions on StackOverflow and found that one proposed solution was to upgrade to 1.9.3. I did some Googling and found out that I wasn’t the only one who was having issues with Rails 3 and Ruby 1.9.2. WTF?!? This was something that would seriously slow me down. My minimal set of tests took over one and a half minutes to run. I then started coding, wrote some simple tests then ran rake test from the console. However, as this only needs to be done once (or occasionally twice) per session, I didn’t think much more of it. Whilst ensuring that everything worked as expected, I noticed was that WEBrick was very slow to boot. The remote server currently runs Ruby 1.9.2 and Rails 3.x, so this is what I installed on my local machine. Your terminal should now be a Bash instance.I had recently started work on a Rails project and was setting up my local dev environment which I wanted to make it as similar as possible to the environment on the server I will deploy to. Open a new Command Prompt or PowerShell window and type bash. Make sure all your packages and repositories are up to date. You must have Windows Subsystem for Linux enabled. Installing the Windows Subsystem for Linux. If you are using Windows 10 version 1607 or later, another option to run Jekyll is by That’s it, you’re ready to use Jekyll! Installation via Bash on Windows 10 If the error persists, please open a RubyInstaller issue. Reboot your system and run jekyll -v again. You may receive an error when checking if Jekyll has not been installed properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |