diff options
Diffstat (limited to 'v1.5/gemfile_ruby.html')
| -rw-r--r-- | v1.5/gemfile_ruby.html | 99 |
1 files changed, 0 insertions, 99 deletions
diff --git a/v1.5/gemfile_ruby.html b/v1.5/gemfile_ruby.html deleted file mode 100644 index 1f28671133..0000000000 --- a/v1.5/gemfile_ruby.html +++ /dev/null @@ -1,99 +0,0 @@ -<!DOCTYPE html> -<html> - <head> - <title>Bundler: The best way to manage a Ruby application's gems</title> - <meta content='text/html; charset=UTF-8' http-equiv='Content-Type'> - <meta content='276VSYOko8B8vIu1i8i5qbj7_ql5PXo0dU69XQy-SL' name='globalsign-domain-verification'> - <link href='/images/favicon.png' rel='shortcut icon' type='image/png'> - <link href="/stylesheets/application.css" media="screen" rel="stylesheet" type="text/css" /> - </head> - <body> - <div id='body'> - <div id='header'> - <a class="image" href="/"><img width="725" alt="The best way to manage your application's dependencies" src="/images/gembundler.png" /></a> - </div> - <div id='container'> - <div id='contents'> - <h2>Specifying a Ruby Version</h2> - <div class='contents'> - <div class='bullet'> - <div class='description'> - Like gems, developers can setup a dependency on Ruby. This makes your app fail faster in case you depend on specific features in a Ruby VM. This way, the Ruby VM on your deployment server will match your local one. You can do this by using the <code>ruby</code> directive in the <code>Gemfile</code>: - </div> - <pre class="highlight ruby"><span class="n">ruby</span> <span class="s1">'RUBY_VERSION'</span><span class="p">,</span> <span class="ss">:engine</span> <span class="o">=></span> <span class="s1">'ENGINE'</span><span class="p">,</span> <span class="ss">:engine_version</span> <span class="o">=></span> <span class="s1">'ENGINE_VERSION'</span><span class="p">,</span> <span class="ss">:patchlevel</span> <span class="o">=></span> <span class="s1">'RUBY_PATCHLEVEL'</span>
</pre> - </div> - <div class='bullet'> - <div class='description'> - If you wanted to use JRuby 1.6.7 using Ruby 1.9.3, you would simply do the following: - </div> - <pre class="highlight ruby"><span class="n">ruby</span> <span class="s1">'1.9.3'</span><span class="p">,</span> <span class="ss">:engine</span> <span class="o">=></span> <span class="s1">'jruby'</span><span class="p">,</span> <span class="ss">:engine_version</span> <span class="o">=></span> <span class="s1">'1.6.7'</span>
</pre> - </div> - <div class='bullet' id='patchlevel'> - <div class='description'> - It's also possible to restrict the patchlevel of the Ruby used by doing the following: - </div> - <pre class="highlight ruby"><span class="n">ruby</span> <span class="s1">'1.9.3'</span><span class="p">,</span> <span class="ss">:patchlevel</span> <span class="o">=></span> <span class="mi">448</span>
</pre> - </div> - <div class='bullet'> - <div class='description'> - Bundler will make checks against the current running Ruby VM to make sure it matches what is specified in the <code>Gemfile</code>. If things don't match, Bundler will raise an Exception explaining what doesn't match. - </div> - <pre class="highlight plaintext">Your Ruby version is 1.8.7, but your Gemfile specified 1.9.3
</pre> - </div> - <div class='bullet'> - <div class='description'> - Both <code>:engine</code> and <code>:engine_version</code> are optional. When these options are omitted, this means the app is compatible with a particular Ruby ABI but the engine is irrelevant. When <code>:engine</code> is used, <code>:engine_version</code> must also be specified. - </div> - </div> - <div class='bullet'> - <div class='description'> - Using the <code>platform</code> command with the <code>--ruby</code> flag, you can see what <code>ruby</code> directive is specified in the <code>Gemfile</code>. - </div> - <pre class="highlight plaintext">ruby 1.9.3 (jruby 1.6.7)</pre> - <a href="/v1.5/bundle_platform.html">Learn More: bundle platform</a> - </div> - <div class='bullet'> - <div class='description'> - In the <code>ruby</code> directive, <code>:patchlevel</code> is optional, as patchlevel releases are usually compatible and include important security fixes. The patchlevel option checks the <code>RUBY_PATCHLEVEL</code> constant, and if not specified then bundler will simply ignore it. - </div> - </div> - </div> - </div> - </div> - </div> - <div id='footer'> - <img src="/images/emocow.png" /> - <img src="/images/panda.jpg" /> - <div class='spacer'></div> - <div id='credits'> - <p> - Many thanks to Bundler's <a href="/contributors.html">contributors</a> - and <a href="/sponsors.html">sponsors</a> - </p> - </div> - <div class='spacer'></div> - <img src="/images/bundler-small.png" /> - </div> - <a href='http://github.com/bundler/bundler/' id='github'> - <img alt='Fork me on GitHub' src='http://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png'> - </a> - <div id='prod-versions'> - Docs: - <a href="/v0.9/">v0.9</a> - <a href="/v1.0/">v1.0</a> - <a href="/v1.1/">v1.1</a> - <a href="/v1.2/">v1.2</a> - <a href="/v1.3/">v1.3</a> - <a class="current" href="/v1.5/index.html">v1.5</a> - <a href="/">v1.6</a> - </div> - <script> - (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ - (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), - m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) - })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); - ga('create', 'UA-39559982-1', 'bundler.io'); - ga('send', 'pageview'); - </script> - </body> -</html> |