# 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:** 14

<div class="post-metadata">

### Author: ![JackNZ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jacknz/32/525193_2.png) [@JackNZ](https://meta.discourse.org/u/JackNZ)
#### Post date: [14 Ottobre 2025, 3:45am UTC](https://meta.discourse.org/t/is-docker-image-discourse-discourse-considered-safe-and-production-ready/380646/14 "2025-10-14T03:45:06Z")

</div>

Situazione simile, stavo cercando un modo rapido per avviare Discourse in una configurazione Docker Compose per facilitare agli sviluppatori la creazione di un’integrazione SSO. Questo sembra funzionare alla grande (configurazione di seguito per chi fosse interessato):

> **docker-compose.yml**
>
> ```yaml
> volumes:
> redis_data: {}
> discourse_data: {}
> discourse_postgres: {}
> discourse_postgres_data: {}
> 
> services:
> mailpit:
> image: docker.io/axllent/mailpit:latest
> container_name: mailpit
> ports:
> - '8025:8025'
> 
> redis:
> image: redis:7-alpine
> container_name: redis
> volumes:
> - redis_data:/data
> ports:
> - '6379:6379'
> command: redis-server --appendonly yes
> 
> discourse_db:
> image: discourse/postgres
> container_name: discourse_db
> volumes:
> - discourse_postgres:/var/lib/postgresql
> - discourse_postgres_data:/var/lib/postgresql/data
> environment:
> - POSTGRES_DB: discourse
> - POSTGRES_USER: admin
> - POSTGRES_PASSWORD: admin_password
> - DB_USER: discourse_user
> - DB_PASSWORD: discourse_user_password
> 
> discourse:
> image: discourse/discourse:3.5.1
> container_name: discourse
> depends_on:
> - discourse_db
> - redis
> - mailpit
> ports:
> - '80:80'
> volumes:
> - discourse_data:/shared
> environment:
> - DISCOURSE_HOSTNAME: localhost
> - DISCOURSE_DEVELOPER_EMAILS: admin@example.com
> - DISCOURSE_DB_HOST: discourse_db
> - DISCOURSE_DB_PORT: 5432
> - DISCOURSE_DB_NAME: discourse
> - DISCOURSE_DB_USERNAME: discourse_user
> - DISCOURSE_DB_PASSWORD: discourse_user_password
> - DISCOURSE_REDIS_HOST: redis
> - DISCOURSE_REDIS_PORT: 6379
> - DISCOURSE_SMTP_ADDRESS: mailpit
> - DISCOURSE_SMTP_PORT: 1025
> - DISCOURSE_SMTP_ENABLE_START_TLS: false
> - DISCOURSE_SMTP_AUTHENTICATION: none
> - LANG: en_US.UTF-8
> 
> ```

Attendo con ansia di conoscere i piani o le tempistiche future, mi piacerebbe poter eseguire questo in qualcosa come Digital Ocean App Platform (qualcosa che i clienti potrebbero gestire con meno conoscenze tecniche).

---

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