It also defines ActiveSupport::Railtie, which is one of the ways to extend your Rails application. All these additions have hence been collected in this bundle as way to gather all that sugar that makes Ruby sweeter.” This means, in essense, that ActiveSupport is THE building blocks of Rails, including abstractions for caching, JSON support, unicode support, and notifications. In the case of the vanilla Rails install, it uses the json_puregem.ĪctiveSupport is “a collection of various utility classes and standard library extensions that were found useful for Rails. MultiJSON (by Intridea, who do great stuff) allows for multiple JSON backends, detecting and leveraging the best one. What are those gems? What is their purpose? When we installed Rails, it also installed several other gems. As a special bonus, here is a way to significantly speed up your gem installs by setting options in your Gem configuration file. Finally, you can put any of these options into your ~/.gemrc file if you find yourself typing the same options over and over again. Looking over the available options, it’s easy to see how RVM leverages RubyGems to keep gemsets isolated. RubyGems allows us to specify items, such as, a specific version (which we’ve seen), an install destination, whether or not to install documentation, whether or not to install dependencies, as well as specifying a source for searching for gems. Now you know what the “–pre” option does when installing the Rails gem, but what other options are there? “gem install” takes many options, which we can see here. Thanks to RVM, we can muck about with any of the pre-release software without contaminating the rest of our development environment. Where we can see that Rails follows a pattern of starting with a “beta” release, followed by 4 or 5 release candidates, before going stable.
The Rails gem has many dependencies, which are satisfied by other gems, but the actual Rails gem is just an executable. In fact, it may surprise you to know that the only thing the Rails gem includes is the rails executable. What you may not know is where Rails executable lives. As you probably know, the way to generate a new Rails application is by typing this at the command prompt. Rvm you can verify with a quick rvm info.
Selecting the Interpreterįirst things first, make sure you open up a terminal and switch to our RVM Ruby interpreter and gemset, which is MRI 1.9.2 and rubysource, respectively.
Again, this series attempts to give you a bit of a deeper dive into getting started with Rails, so we will go through some of the options available when first creating your world-changing Rails application, as well as the gems that are installed along with Rails. Continuing from my last post about RVM, this time we’ll install Rails.
0 kommentar(er)
