# Inject patch in Docker Installation

**URL:** <https://meta.discourse.org/t/inject-patch-in-docker-installation/48994>\
**Category:** Self-hosting\
**Created:** [August 22, 2016, 11:39am UTC](https://meta.discourse.org/t/inject-patch-in-docker-installation/48994 "2016-08-22T11:39:13Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [August 24, 2016, 10:25pm UTC](https://meta.discourse.org/t/inject-patch-in-docker-installation/48994/9 "2016-08-24T22:25:40Z")

</div>

Sorry I misunderstood what you were saying.

As far as maintaining a private fork of Discourse, here’s the difference:

> [@dorianamouroux](#):
>
> I did it for gollum wiki it works like a charm ( **the project is barely maintained now though** )

Discourse has several people employed full-time to add features and fix bugs (including security bugs), as well as a large number of fantastic contributors from all over the Internet. There’s a pretty good chance the changes in a private fork is going to end up conflicting with the changes made in mainline fairly often, necessitating manual review and modification of the local patches.

---

_[View the full topic](https://meta.discourse.org/t/inject-patch-in-docker-installation/48994)._