title: LearnBoost's Up for Node.js doesn't seem to restart my apps correctly?
body: <p>I've been using <a href="https://github.com/LearnBoost/up" rel="nofollow">LearnBoost's Up</a> for Node.js as a way for me to have zero-downtime when I'm changing or uploading new code for my projects. Because my projects are using web sockets (via <a href="http://socket.io/" rel="nofollow">Socket.io</a>) I don't want my app to cold reload as those real-time connections will be lost.</p>
  
  <p>I'm using LearnBoost's Up as it says to offer "zero-downtime reloads", but it never seems to reload my apps correctly once I've changed code and I always need to exit my Node app and restart it again manually to get it to run the new code.</p>
  
  <p>I have the latest version of Up running (which is <a href="https://github.com/LearnBoost/up/tags" rel="nofollow">0.2.1</a> as of writing) on both my local Mac machine and my Linux server.</p>
  
  <p>I use this on my local dev to run my Node app:</p>
  
  <pre><code>NODE_ENV=development up --watch --port 9001 init.js
  </code></pre>
  
  <p>But say I do something simple (but drastic) like change the static media folder for the app or alter some of the routing (for example) in the Terminal it looks like it's restarted my app, but the actual change doesn't happen. The only way is for me to exit and restart the Node app manually. It's the same on my remote server too and obviously this isn't right.</p>
  
  <p>Am I using this correctly?</p>