title: Nodemon server perpetuality and runtime log issue
body: <p>I have a sailsjs app on AWS EC2, which I have been running till now using forever. I have two adantages using forever:</p>
  
  <p>1) <strong>Perpetuality:</strong> I can use the CLI <code>forever start app.js</code> or <code>forever restart app.js</code> and then app starts running and keeps on running till I stop it with the command <code>forever stop app.js</code>. So, the app does not stop even when I close my terminal. The process keeps on running.</p>
  
  <p>2) <strong>Runtime Log:</strong> I have a <code>.forever</code> directory that has a log file, while on real time records the server logs, and when I check the log using <code>tail -f file_name.log</code>, I get to see run time logs.</p>
  
  <p>However there is a disadvantage: Every time I upload a new/modified server file, I have to restart the app manually. To get rid of this, I am switching from forever to nodemon.</p>
  
  <p>From the documentation provided by Nodemon, I cant figure out how can I replicate the two advantages, as mentioned above, from Nodemon too. Will be a great help if anyone can guide me on how to start my nodejs app using nodemon so that it can keep running even after closing the terminal on my side, and how to watch runtime log of server.  </p>