# Is Docker image discourse/discourse veilig en klaar voor productie?

**URL:** https://meta.discourse.org/t/is-docker-image-discourse-discourse-considered-safe-and-production-ready/380646
**Category:** Self-hosting
**Tags:** hosting
**Created:** [28 augustus 2025 om 00:26 UTC](https://meta.discourse.org/t/is-docker-image-discourse-discourse-considered-safe-and-production-ready/380646 "2025-08-28T00:26:57Z")
**Posts on this page:** 1
**Showing post:** 24

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [31 maart 2026 om 20:24 UTC](https://meta.discourse.org/t/is-docker-image-discourse-discourse-considered-safe-and-production-ready/380646/24 "2026-03-31T20:24:44Z")

</div>

> [@Yannovitch](#):
>
> I almost got it to work, but the mail sending wasn’t working.  
> I suppose it was because I have caddy as a reverse proxy.

Unless you’re somehow having Caddy proxy your outgoing email, I don’t think it’s related.

> [@Yannovitch](#):
>
> I suppose I have to make it use a socketed example, but I don’t know how to modify the app.yml inside the docker-compose discourse config.

You don’t have to make it socketed, you can just refer to the docker name and/or IP. [Discourse working with jwilder /nginx proxy & acme-companion - #7 by Steve\_Emerson](https://meta.discourse.org/t/discourse-working-with-jwilder-nginx-proxy-acme-companion/217059/7) talks about using the socketed template and a bunch of other stuff.

---

_[View the full topic](https://meta.discourse.org/t/is-docker-image-discourse-discourse-considered-safe-and-production-ready/380646)._