nexus

nexus - remote program installation and control (work in progress/proof of concept)

     _______________________________
    /    ___  ___  _ _  _ _  ___    \
    |   |   || -_||_'_|| | ||_ -|   |
    |   |_|_||___||_,_||___||___|   |
    \_____________________________  / ____       ___
                                  \| / .  \  .-´/   \`-.
                                     \____ \/   \___/   \__
                                          \_`---´___`---´-´
                                           /../..\ /..\..\

• nexus provides a cli and a dnode-interface to install, uninstall, start, stop and observe local and remote programs (npm packages).
• running programs are require('child_process').spawn'ed child-processes of monitor-servers (dnode-clients). the monitor-servers will try to reconnect to the nexus-server (dnode-server). the nexus-server is also a require('child_process').spawn'ed child-process of a monitor-server - which itself will try to reconnect to its own child-process.
• all the config, logs and programs live in ~/.nexus by default.
• nexus shells out into npm, is built upon dnode and is inspired by forever.
• nexus is still super-alpha.

install

• install node
• install npm
• npm install nexus -g
• npm test nexus

cli

nexus [-r <remote>] [-c <path to configFile>] [<command> [<options>]]

commands:

    version   .. print version-number
    config    .. get/set config
    ls        .. list installed packages
    install   .. install packages
    uninstall .. uninstall packages
    ps        .. list of current running (and crashed) programs
    start     .. start a program
    restart   .. restart a running (or max crashed) program
    stop      .. stop a running program
    stopall   .. stop all running programs
    runscript .. execute a script, defined in the package.json
    logs      .. access log-files
    subscribe .. subscribe to events
    server    .. start/stop/restart the nexus-server
    help      .. try `nexus help <command>` for more info

note: ps, restart, stop, stopall, subscribe and `logs clean`
      only work with a local or remote running nexus-server.

config

the nexus-cli will create a ~/.nexus-directory if it doesnt exist. you can create a ~/.nexus/config.js-file which exposes a json-object, or just a ~/.nexus/config.json - it will be require()'ed.

at least, socket or port (or both) must be set - everything else is optional. if no socket is defined, the cli will use the key and cert to connect to the local nexus-server.

{ socket  : '/path/to/socket'  // if set, the nexus-server will listen on that port
                               // local cli and monitor-servers will connect to it
, port    : 12345              // if set, the nexus-server will listen on that port
                               // remote nexus-cli can connect (see -r option)
, host    : '0.0.0.0'          
, key     : <key>              // if set, the nexus-server uses tls
, cert    : <cert>             // if set, the nexus-server uses tls
, ca      : '/path/to/ca'      // every file in that directory will be read into the ca
, remotes :                    // can be used with the cli: `nexus -r foo ps`
  { local : { port:12345, key:<key>, cert:<cert>, host:'0.0.0.0' }
  , foo   : { port:12346, key:<key>, cert:<cert>, host:'foo.com' }
  , bar   : { port:12347, key:<key>, cert:<cert>, host:'bar.com' }
  }
} 

api

TBA