Self-Hosting Moose with Docker Compose, Redis, Temporal, Redpanda and ClickHouse
6 comments
·May 19, 2025Callicles
pitah1
I have a small open-source project, that uses docker compose behind the scenes, to help startup any service. You can look to add it in (or I am also happy to add it in) and then users are one command away from running it (insta moose). Recently just added in lakekeeper and various data annotation tools.
insta-infra: https://github.com/data-catering/insta-infra
Havoc
For everyone else confused too…think moose in this context is probably this:
oatsandsugar
Actually, this https://github.com/514-labs/moose
mitchellsuzuki
this is too perfect. as an SRE who often needs to hand roll my own deployments in k8s or w/e medium, these are the docs that really accelerate my path to production.
faeeafeae
[dead]
I put this Docker-Compose recipe together to make kicking the tires on Moose—our open-source data-backend framework—almost friction-less.
What you get:
• A single docker compose up that spins up ClickHouse, Redpanda, Redis and Temporal with health-checks & log-rotation already wired.
• Runs comfortably on an 8 GB / 4-core VPS; scale-out pointers are in the doc if you outgrow single-node.
• No root Docker needed; the stack follows the hardening tips ClickHouse & Temporal recommend.
Why bother?
Moose lets you model data pipelines in TypeScript/Python and auto-provisions the OLAP tables, streams and APIs—cuts a lot of boilerplate. Happy to trade notes on the approach or hear where the defaults feel off.
Docs: https://docs.fiveonefour.com/moose/deploying/self-hosting/de...
18-min walkthrough video: https://www.youtube.com/watch?v=bAKYSrLt8vo