title: On AppFog or CloudFoundry, how can app update be forced?
body: <p>I am deploying an Django/Python app on <a href="http://www.appfog.com" rel="nofollow">AppFog</a> (which is based on <a href="http://www.cloudfoundry.com/" rel="nofollow">CloudFoundry</a>). Until recently, updates could easily be deployed using the <code>af update</code>command. Here's an example:</p>
  
  <p>consider a local file <code>settings.py</code> with some changes, e.g.:</p>
  
  <pre><code>  ...
    # CHANGES
    MY_SETTING = 'TEST'
    ...
  </code></pre>
  
  <p>Previously, when I issued <code>af update myapp</code>, waited until the app restartd and then look at the <code>settings.py</code> on the app instance (<code>af files myapp app/settings.py</code>), I would get back exactly the above, changed file.</p>
  
  <p>Now all of a sudden, when I do the same steps, the changes are not applied. The restarted app always uses the old version of settings.py (and any other files that changed in between). I have tried to issue <code>af update myapp --no-resources</code> to force upload of all files, or to <code>af push</code> to a different app -- same result.</p>
  
  <p>How can I force AppFog or CloudFoundry in general to drop whatever package it stores for my app and accept a fresh update?</p>