# Is the Packaging Subflow Modules Documentation Obsolete or needs update?

**URL:** https://discourse.nodered.org/t/is-the-packaging-subflow-modules-documentation-obsolete-or-needs-update/61751
**Category:** General
**Created:** [25 April 2022 12:14 UTC](https://discourse.nodered.org/t/is-the-packaging-subflow-modules-documentation-obsolete-or-needs-update/61751 "2022-04-25T12:14:46Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Shan](https://avatars.discourse-cdn.com/v4/letter/s/7ab992/32.png) [@Shan](https://discourse.nodered.org/u/Shan)
#### Post date: [25 April 2022 12:52 UTC](https://discourse.nodered.org/t/is-the-packaging-subflow-modules-documentation-obsolete-or-needs-update/61751/3 "2022-04-25T12:52:39Z")

</div>

@knolleary Thanks for reaching out I am currently documenting the potential workflow In the following

> [@How to package node-red subflows into a dedicated Node-Red Docker Container?](https://discourse.nodered.org/t/how-to-package-node-red-subflows-into-a-dedicated-node-red-docker-container/61745):
>
> I have created a subflow for the standard mqtt in and mqtt out nodes which sets the broker address accordingly (docker container names of the MQTT broker) and is made available for the use in the node pallete. The node pallete looks as follows: [image] The subflow is very simple, it is just a wrapper around the mqtt in and mqtt out nodes but the mqtt properties are configured to the broker address instead of localhost Internal MQTT In Node [image] Internal MQTT Out Node [image] Document…

I am just about to put an update to what the status is and what the workaround currently is.

---

_[View the full topic](https://discourse.nodered.org/t/is-the-packaging-subflow-modules-documentation-obsolete-or-needs-update/61751)._