# توافق الفرع المستقر مع discourse\_docker والإضافات

**URL:** <https://meta.discourse.org/t/stable-branch-compatibility-with-discourse-docker-and-plugins/117679>\
**Category:** Self-hosting\
**Tags:** stable\
**Created:** [14 مايو 2019، 10:54ص UTC](https://meta.discourse.org/t/stable-branch-compatibility-with-discourse-docker-and-plugins/117679 "2019-05-14T10:54:51Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![crispygoth](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@crispygoth](https://meta.discourse.org/u/crispygoth)\
**Post date:** [15 مايو 2019، 3:43م UTC](https://meta.discourse.org/t/stable-branch-compatibility-with-discourse-docker-and-plugins/117679/25 "2019-05-15T15:43:59Z")

</div>

I would personally agree with the idea of tagging `discourse_docker` with the same version as the stable release. We currently use Puppet to automate the process of bootstrapping new Docker containers, which we pin to a specific stable release of Docker (we’re in the kind of corporate environment where the idea of running “beta” software is basically a no-go). It’d be nice if I could use that same version number as a tag in the `discourse_docker` repo and know that the version of the launcher I’m using is going to be able to build the version of Discourse I want to build.

---

_[View the full topic](https://meta.discourse.org/t/stable-branch-compatibility-with-discourse-docker-and-plugins/117679)._