We're going to create a Node.js application that will act as a long-running daemon fulfilling the responsibilities of interacting with the client web users and monitoring a file spool directory where JUNOS OS devices will upload their configuration reports following a commit event:
- Create a directory to keep the application components in one place. We're going to use some external library components and modules, and Node.js implements third-party linkage by storing the required modules in a node_modules directory within the dependent app, rather than installing modules system-wide. This goes some way to help create a self-contained application:
$ cd config-monitor
- Install into your application development directory ...