Deploy node.js with zero downtime using naught

I started using naught for node.js deployment (
I have a folder in Ubuntu Server containing my node.js(express) app.
I deployed it using “naught start app.js” from this folder.
Now I would like to redeploy/update my code with zero downtime.
What should I do?
Suppose I have my code on a git server, do I “git pull origin master” in the same folder and then “naught deploy” to deploy the new code? Or maybe I need to pull the new code to a new folder and deploy the new code in another way?

  • MEAN Project - Organization
  • Locally-installed modules in node.js
  • Using nodes git-rev on Heroku
  • How can I sync the documents of shareJS with a fileSystem
  • How to organize separate client and server repositories for both development and deployment?
  • How to load private git repository as package at azure website?
  • How to change git from Chinese to English in mac
  • How to have 2 git users on one computer?
  • Bitnami GitLab 5.0 and git & Eclipse EGit quick start
  • Convert git repository file encoding
  • Notification on failed GitHub WebHooks?
  • Git rebase non-interactive for last two commits - write a batch file
  • One Solution collect form web for “Deploy node.js with zero downtime using naught”

    Pulling the latest changed from Git and calling ‘naught deploy’ should do the trick. You don’t need to clone your code a different directory.

    Notice that the ‘deploy’ command expects an .ipc file, and by default looks for it in the same directory from which you called deploy. If, when starting naught you specified a different location for the .ipc file, then you should call deploy with that location.

    So for example, if you did:

    naught start app.js --ipc-file /var/run/naught.ipc

    Then when deploying use:

    naught deploy /var/run/naught.ipc

    At BigPanda we use naught in production this way, and it works perfectly.

    Git Baby is a git and github fan, let's start git clone.