@int3gra/manager

Integration supervisor for int3gra. Spawns, monitors, and manages integration instances via PM2.

Installation

npm install -g @int3gra/engine @int3gra/cli @int3gra/manager

PM2 must also be installed globally:

npm install -g pm2

Commands

Run from the directory containing registry.json:

integra-manager start [--env <file>]   # Start all enabled integrations
integra-manager stop <id>              # Stop an integration
integra-manager restart <id>           # Restart an integration
integra-manager status                 # Show status, lifecycle, env, uptime
integra-manager logs <id>             # Tail integration logs
integra-manager enable <id>            # Enable an integration in the registry
integra-manager disable <id>           # Stop and disable an integration

registry.json

The manager reads a registry.json file that lists all known integrations:

{
  "integrations": [
    {
      "id":          "my-sn-jira",
      "path":        "./my-sn-jira",
      "enabled":     true,
      "description": "Syncs ServiceNow incidents to Jira",
      "schedule":    "*/5 * * * *",
      "max_ttl":     240
    },
    {
      "id":          "my-jira-sn",
      "path":        "./my-jira-sn",
      "enabled":     true,
      "description": "Receives Jira webhooks and creates SN incidents"
    }
  ]
}

Lifecycles

| Lifecycle | How it runs | |---|---| | (absent) | Run-once — starts, executes entry process, exits | | scheduled | TrafficController fires entry on cron schedule | | listener | Long-lived Fastify HTTP server, autorestart: true |

Lifecycle is declared in each integration's integra.json. A schedule field in registry.json makes an integration scheduled.

Links

• Documentation & full README
• GitHub
• npm — @int3gra/engine
• npm — @int3gra/cli

License

BSL 1.1 — free to use commercially as a component of your own products. May not be resold or repackaged as a standalone product. Converts to Apache 2.0 on 2030/12/31. See LICENSE and NOTICE for details.