Thankfully it's pretty easy to update the certs. This error comes up because the security certificates used by gem are out of date. Oh no! SSL Hell! Apparently recently updated their SSL Certificates which requires clients to also update. State=SSLv3 read server certificate B: certificate verify failed. Unable to download data from - SSL_connect returned=1 errno=0 Just follow the normal instructions for installing DevKit and install it for each of the Ruby versions you want to use, obviously using the version of Ruby for which you are installing DevKit.Īs a last step, install the json gem to make sure DevKit is installed correctly.ĮRROR: Could not find a valid gem 'json', here is why: I generally store the DevKit next to the version of Ruby to which it belongs, for example, C:\ruby\Ruby193\devkit where Ruby193 is the folder containing the 193 version of Ruby that I registered with uru. DevKit is just an archive that you unzip to a specific location and run an install script to copy some files into the right places so Ruby can use them. You'll need this to install any gems that require native extensions such as json. The last step I took was installing the Ruby Windows DevKit. 'jruby' is not recognized as an internal or external command, 'ruby' is not recognized as an internal or external command, > Now using jruby 1.7.18 tagged as `jruby` Now switching my environment to use JRuby is as simple as. Once installed I changed the tag associated with JRuby to be a little easier to remember.Īt this point, I'm up and running. The next step is to register each Ruby version using the uru command line.Ĭ:\> uru admin add c:\ruby\jruby-1.7.18\bin\ Step 3: Register your Ruby Installations with uruīy this point I have installed all of my Ruby versions to the C:\ruby\ directory with none on the path. The main thing is to just be careful about what gets added to your path when performing the installations. I don't have any Ruby versions on my path and instead choose the Ruby version I want to use explicitly each time. I installed different versions of Ruby using the Ruby Windows Installer and also the latest JRuby. If you choose to have a system Ruby then that should be the only one you allow to be added to the path. You may have up to 1 "system" Ruby when using uru. Next, download and install the Ruby versions you want. Next, follow the instructions on the uru website. Basically, just run. I have a generic "tools" folder for things like this. To do this, download the zip and unpack it to a place on your path. If you're trying to run multiple Ruby versions on Windows you should give uru a try.įirst, download and install uru. Here's the steps I used to overcome those problems. That said, when first g etting uru up and running I did run into a few snags. I've been using uru for close to a year now and it's worked out very well for me. Thankfully, now there's uru, a cross platform Ruby environment manager that works on Windows, Linux, and OS X. Until recently, the only option on Windows was pik, a woefully out of date and problematic open source project that is no longer under active development (I'm not going to even bother linking to it). The basic idea is to make it easier to switch between different Ruby versions on the command line so that it's easier to test and develop against multiple projects. One thing that is particularly annoying is the lack of a Ruby version manager. Version managers are a great idea. While the core language works really well across different platforms, as a predominantly Windows user, I find that Ruby sometimes runs into problems in odd situations. I eventually settled on Ruby as my scripting language of choice. Scripts are easy to write, easy to share, and good enough to get the job done. An interpreted scripting language is the perfect choice for one off tests, tedious text manipulation, automated tasks, and simple tools. Learn to use it really, really well.Ĭompiled programming languages obviously have a purpose, but lightweight, interpreted scripting languages are an important tool as well. My undergraduate software engineering professor was awesome. Here's one bit of advice he shared during his course that really stuck with me over the years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |