Why doesn't a UMH docker compose version exist wit...
# umh-supportd
Diederik
11/19/2025, 12:52 PMA docker compose with the node-red, timescaledb,... included already.
Then you have both the umh core for remote instances and a umh classic as main instance but with easier managebility than Kubernetes.
j
Jermuk
11/19/2025, 1:18 PM@krgrsebastian has a template for this, but we don't want to ship it as part of our product. maybe we can put it somewhere here in the dsicord for the community to find?
d
Diederik
11/19/2025, 1:34 PMthat wuold be nice! 🙂
s
sheetmetalconnect
11/22/2025, 9:52 AMWould also love this
d
Diederik
11/22/2025, 1:42 PM@krgrsebastian would you be open to share this? 🙂 what context should we have on this compose file from your side? Why you think we should (not) use it?
j
Jermuk
11/24/2025, 3:30 PMi am currently preparing something here 🙂
Jermuk
11/24/2025, 3:30 PMit would only be a template, but better something than nothing i guess
Jermuk
11/26/2025, 2:36 PMi am currently working on it, and the state can be found here (if anyone wants to sneak peak). but basically I noticed that we dont have a good bridge template, so this is where @daniel_umh is now taking over 🙂
the PR in question: https://github.com/united-manufacturing-hub/united-manufacturing-hub/pull/2340
Jermuk
11/26/2025, 2:37 PM(in the sense of sometimes "something" is better than "nothing, but in a couple of months a perfect solution")
r
runeston3
12/09/2025, 7:15 PMI will see if i can share the manifests for kubernetes. Since i am doing our third migration now i am setting up the umh-core in our kubernetes. Separate timescale with init-script for the database, hivemq for mqtt, nodered and grafana as separate manifests/helmcharts. I will start working with a kafta2postgres bridge tomorrow to get the same functionallity as before with _historian for automatic insert to db.
j
Jermuk
12/10/2025, 8:12 AM@daniel_umh is also working on it from our side
Jermuk
12/10/2025, 8:12 AM#DanielAndDaniel
Jermuk
12/10/2025, 8:12 AM*#DanielHAndDaniel
r
runeston3
12/10/2025, 4:30 PMi have all the manifests done. will see if i can upload to my github. did the first version of the kafka2posgres today but did not had the time to finish it.
s
sheetmetalconnect
12/22/2025, 2:44 PMHey all, what's the status on this one? Can I contribute? I decided to take some time these weeks to migrate my first PoC project that's running on classic to UMH Core (with updated grafana, nodered etc.)
j
Jermuk
12/23/2025, 10:44 AMJermuk
12/23/2025, 11:13 AMfor the bridges to timescale, you would still need to create your own standalone flow thatwrites to timescale from uns, but we are working here on giving a good example
r
runeston3
12/24/2025, 7:35 AMi have set up a bridge for timescale based on the umh-classic bridge which i have tested that works. i will see after christmas if i can upload that along with the manifests for kubernetes.
s
sheetmetalconnect
12/29/2025, 10:06 AMOkay! I created this https://github.com/SheetMetalConnect/UMH-Core-Stack
sheetmetalconnect
12/29/2025, 10:08 AMGrafana already comes with connections to the timescale.
sheetmetalconnect
12/29/2025, 10:09 AM- HiveMQ (MQTT broker)
- Node-RED
- Portainer
- Pre-configured database schema (tables: asset, tag, tag_string)
- Example historian flow in `docs/historian-flow.md
d
daniel_umh
01/15/2026, 10:40 PMWe have compiled guidance on how to set up a baseline docker compose stack with umh-core.
The base recommendations we want to make are umh-core + pgbouncer|timescaledb + Grafana. For the time being we don't want to include documentation for setting up NodeRED/HiveMQ.
You can find it here - but looking at your stack you likely won't need it 🙂
https://docs.umh.app/production/deployment/docker-compose
s
sheetmetalconnect
01/19/2026, 8:34 PMI will compare and combine this. Thanks for organizing this so neatly!
4 Views