← all publishers

mariot

@mariot source repo

Report this profile Claim this profile

• 4 skills
• 0 followers
• 7 hours ago last updated

1. ▌
   Spawn Xtm Suite · mariot

   Spins up any combination of the XTM suite — OpenAEV, OpenCTI, or both — each as its own isolated Docker Compose stack with its own XTM Composer instance, from released images or a local build. Use when asked to test the suite end-to-end, run OpenAEV and OpenCTI together, or when the specific platform isn't yet decided.
   0 installs
2. ▌
   Test With Suite · mariot

   Uses a spawned XTM suite stack (OpenAEV, OpenCTI, or both — see spawn-xtm-suite) to test something live: a platform feature/change via its UI or API, or a connector (an OpenAEV injector/executor, or an OpenCTI collector/import connector) deployed through XTM Composer. Every spawn already includes its own XTM Composer instance in one call — Composer just isn't the focus unless you're specifically testing a connector through it. Use when asked to verify behavior against a real running instance rather than just reading code.
   0 installs
3. ▌
   Spawn Openaev Stack · mariot

   Spins up an isolated OpenAEV Docker Compose stack (Postgres, Silo/MinIO, RabbitMQ, Elasticsearch, Mailpit, XTM Composer) either from a released image or built from a local checkout, and reports the URL + admin credentials once healthy. Use when asked to run/test OpenAEV locally, verify a change against a live instance, or test a connector (injector, executor) end-to-end.
   0 installs
4. ▌
   Spawn Opencti Stack · mariot

   Spins up an isolated OpenCTI Docker Compose stack (Redis, Elasticsearch, Silo/MinIO, RabbitMQ, worker, XTM Composer) from released images, and reports the URL + admin credentials once healthy. Use when asked to run/test OpenCTI locally, verify a connector, or test XTM Composer/OpenAEV interoperability against a real OpenCTI.
   0 installs