feat: Deploy a standalone MISP instance (Dockerized, with users & API keys provisioned)

[hyde-repo]

Description
Set up a standalone, usable MISP deployment via Docker. Provisioning must be automated: create initial users (with at least one or two admins), a reader user and a writer user, and auto-generate their API keys so the instance is ready to consume programmatically right after boot. Deliver a two-stage Dockerfile (builder + runtime/pusher) based on the latest Ubuntu Server LTS, and a docker-compose.yml to build, run, and validate the full stack locally.

Working branch

• feature/misp-standalone-bootstrap

Files / locations

• range42/range42-catalog/03_container_layer/docker/admin/misp-standalone/Dockerfile - two-stage build (builder → runtime)
• range42/range42-catalog/03_container_layer/docker/admin/misp-standalone/docker-compose.yml - full stack (MISP + DB + Redis as required)
• range42/range42-catalog/03_container_layer/docker/admin/misp-standalone/provisioning/ - init scripts for users, orgs, API keys
• range42/range42-catalog/03_container_layer/docker/admin/misp-standalone/.env.example - default admin credentials, org name, base URL, etc.
• range42/range42-catalog/03_container_layer/docker/admin/misp-standalone/README.md - deployment, build & push instructions

Note: paths above are workspace-level for now and may be adjusted later.

Requirements

• Base image: latest Ubuntu Server LTS
• Two-stage Dockerfile (builder + runtime/pusher)
• Bootstrap on first run:
  • 1–2 admin users (configurable via env)
  • 1 reader user (read-only role) with auto-generated API key
  • 1 writer user (publish/contribute role) with auto-generated API key
  • Default org created
  • Base URL, salt, and required MISP settings configured
• API keys exposed via logs or a mounted output file for easy retrieval
• Persistent volumes for DB and MISP files
• Healthcheck on the MISP container
• README documents: build, push, deploy, retrieving API keys, default credentials