README.html

   1 <style type="text/css">
   2 code {
   3         border: 0.1em solid #666;
   4         border-left: 0.2em solid #666;
   5         padding: 0.75em 1em 0.75em 2em;
   6         display: block;
   7 }
   8 #script_gem_manual {
   9         margin: 0;
  10         padding: 0 1em;
  11 }
  12 #script_gem_manual li {
  13         list-style: square;
  14 }
  15 </style>
  16
  17 <h2>Summary</h2>
  18 <p>
  19         script_gem allows you to setup isolated gem environments for your rails
  20         application.
  21 </p>
  22
  23 <p>
  24         It will introduce a top level 'gems' directory which it will be used by
  25         your application. This is a normal rubygems installation. All your gem
  26         commands will work as normal, and you will be responsible for managing this
  27         repository [the script will install rails for you]. The only change in your
  28         normal `flow of things` is that you will use './script/gem' when you want
  29         to deal with the application's gem environment instead of using a global
  30         'gem' command.
  31 </p>
  32
  33
  34 <h2>ChangeLog</h2>
  35 0.1 - made gem
  36 0.0 - no release yet, look at the commits on the repository for more info.
  37
  38
  39 <h2>Contact</h2>
  40 <p>
  41         If you have suggestions or patches - or want to drop me a comment:
  42 </p>
  43 <p style="margin-left: 2em;">
  44         Naitik Shah &lt;naitik.shah [_a_t_] yahoo [_d_o_t] com&gt;
  45 </p>
  46
  47
  48 <h2>Installation</h2>
  49 <p>
  50         <code>
  51                 gem install script_gem
  52         </code>
  53 </p>
  54
  55
  56 <h2>Usage</h2>
  57 <p>
  58         <code>
  59                 <ul id="script_gem_manual">
  60                         <li>[...cd into your app directory]</li>
  61                         <li>script_gem bootstrap</li>
  62                 </ul>
  63         </code>
  64 </p>
  65
  66
  67 <h2>Shared Cache</h2>
  68 <p>
  69         One issue that arises when having isolated gem environments is that you
  70         would have to keep downloading the gems over and over again. To solve this
  71         issue, script gem will share the gem cache directory. This potentially
  72         involves reusing your existing gem cache directory if its writable by the
  73         current user.  The fallback is to create a new shared cache directory as
  74         $HOME/.script_gem/cache. If you want to force a the fallback, explicitly
  75         create that directory (mkdir -p ~/.script_gem/cache) before running the
  76         bootstrap.
  77 </p>
  78
  79
  80 <h2>Usage</h2>
  81 <p>
  82         Ok, what now?
  83 </p>
  84 <p>
  85         Go to your application RAILS_ROOT and run:
  86 </p>
  87 <code>
  88         ./script/gem
  89 </code>
  90
  91
  92 <h2>FAQ</h2>
  93 <p>
  94         Will this affect my existing gem installation?
  95 </p>
  96 <p style="margin-left: 2em;">
  97         NO! Well, except for one tiny thing - its cache might be reused. Check the
  98         'Shared Cache' section for more info.
  99 </p>
 100
 101 <p>
 102         Will I have to keep downloading all the gems over and over?
 103 </p>
 104 <p style="margin-left: 2em;">
 105         NO! Check the 'Shared Cache' section for more info.
 106 </p>