# L'immagine Docker discourse/discourse è considerata sicura e pronta per la produzione?

**URL:** <https://meta.discourse.org/t/is-docker-image-discourse-discourse-considered-safe-and-production-ready/380646>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [28 Agosto 2025, 12:26am 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:** 15

<div class="post-metadata">

**Author:** ![gadicc](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gadicc/32/116696_2.png) [@gadicc](https://meta.discourse.org/u/gadicc)\
**Post date:** [14 Ottobre 2025, 9:03am UTC](https://meta.discourse.org/t/is-docker-image-discourse-discourse-considered-safe-and-production-ready/380646/15 "2025-10-14T09:03:55Z")

</div>

Grazie per aver condiviso, @JackNZ. Non avevo nemmeno notato l’immagine `discourse/postgres` 😅 Dovrò sistemare quello. Ciononostante, condividerò anche dove sono arrivato. Forse più interessante è lo script `start.sh` qui che, sebbene necessiti di un po’ di pulizia, creerà un utente amministratore, una chiave API e disabiliterà i limitatori di frequenza.

> **[discourse2/tests/docker at dev · gadicc/discourse2](https://github.com/gadicc/discourse2/tree/dev/tests/docker)**
>
> Complete Discourse API, strongly typed. Contribute to gadicc/discourse2 development by creating an account on GitHub.

---

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