<h1 id="setup-download">Download preference setup</h1>
<p>The most important of Ray’s setup tasks, <code>rake ray:setup:download</code>, will be run for you automatically the first time you try to install an extension. However you might not have had <code>git</code> installed when you initially installed Ray. If that’s the case you can change your preference by running:</p>
<pre><code>rake ray:setup:download</code></pre>
<h1 id="setup-restart">Server restart preference setup</h1>
<p>Ray’s other setup task, <code>rake ray:setup:restart</code>, can be used to have Ray automatically restart your server whenever necessary, such as after you install a new extension. Currently, Ray supports restarting a single Mongrel, a Mongrel cluster, Phusion Passenger, Thin or Unicorn; note: single Mongrels, Thin and Unicorn need to be running in daemon mode.</p>
<pre><code>rake ray:setup:restart server=mongrel_cluster
rake ray:setup:restart server=mongrel
rake ray:setup:restart server=passenger
rake ray:setup:restart server=thin
rake ray:setup:restart server=unicorn</code></pre>
<h1 id="ext-remote">Adding extension remotes</h1>
<p>Before you get going with remote branches in Ray you’ll need to make sure you’ve setup at least your GitHub username in your global <code>git</code> configuration file.</p>
<pre><code>git config --global github.user your_github_username</code></pre>
<p>That will add a bit of code to your <code>~/.gitconfig</code> file. Ray can then use that information to determine when you’re installing your own extensions. Now when you install from your own repositories Ray will use your private <span class="caps">URL</span> instead of the public one; which means you can push your local changes back to your GitHub repository.</p>
<p>Now you can install your extensions as you normally would with Ray. Then tell Ray which other users you want to track.</p>
<pre><code>rake ray:extension:install name=extension
rake ray:extension:remote name=extension hub=other_user</code></pre>
<p>As you add remotes Ray will setup tracking branches named like “other_user/branch_name” for each branch the remote user has in their repository. Nothing is merged by Ray and you’ll be returned to your current branch after the remote is setup. Just like when you’re using <code>git</code> directly you’ll want to <strong>make sure your current branch is clean</strong> (commit or stash) before adding remotes; and afterward use your normal <code>git</code> workflow to inspect and merge changes.</p>
<h1 id="ext-pull">Pulling extension remotes</h1>
<p>Once you’ve setup a remote repository on an extension you’ll want to pull down the changes occasionally. You can pull in the remote repositories for either a specific extension or all extensions with remotes setup.</p>
<pre><code># pull remotes on a single extension
rake ray:extension:pull name=extension_name
# pull remotes on all extensions
rake ray:extension:pull</code></pre>
<p><strong>Ray does not merge anything into your master branch</strong>, after pulling in changes use your normal <code>git</code> workflow to inspect and merge these changes.</p>
2009-11-22T23:43:36-08:00
118977
advanced-usage
34113
Advanced usage
2009-08-20T16:11:01-07:00
7944