<?xml version="1.0" encoding="UTF-8"?>
<wiki>
  <body>&lt;p&gt;The package updates are triggered by a cron task that runs on the Crantastic &lt;span class=&quot;caps&quot;&gt;VPS&lt;/span&gt;. The update procedures are stored in &lt;code&gt;lib/crantastic.rb&lt;/code&gt;, and uses ActiveResource to send the updates to the live server (Heroku). The cron entry and update scripts are run by the &lt;code&gt;crantastic&lt;/code&gt; user on the &lt;span class=&quot;caps&quot;&gt;VPS&lt;/span&gt;. Note that this user use a full checkout of the crantastic source tree to run the updates. The cron task runs &lt;code&gt;git pull&lt;/code&gt;, though, so the latest version of the code should always be present on the &lt;span class=&quot;caps&quot;&gt;VPS&lt;/span&gt; without manual intervention.&lt;/p&gt;
&lt;p&gt;However, packages/gems are not automatically updated on the &lt;span class=&quot;caps&quot;&gt;VPS&lt;/span&gt;. This can cause problems if gems present in &lt;code&gt;environment.rb&lt;/code&gt; are not yet installed on the &lt;span class=&quot;caps&quot;&gt;VPS&lt;/span&gt;. So currently one has to be careful with this and log in to the &lt;span class=&quot;caps&quot;&gt;VPS&lt;/span&gt; to update gems. This should be automated somehow..&lt;/p&gt;</body>
  <created-at type="datetime">2009-11-26T14:54:31-08:00</created-at>
  <id type="integer">335831</id>
  <permalink>cran-package-updates</permalink>
  <repository-id type="integer">12522</repository-id>
  <title>CRAN Package updates</title>
  <updated-at type="datetime">2009-09-25T02:32:49-07:00</updated-at>
  <user-id type="integer">2651</user-id>
</wiki>
