Discourse 팀 여러분,
현재 다음 주소를 통해 제공되는 Docker 이미지를 평가하고 있습니다: discourse/discourse - Docker Image
해당 이미지는 매우 최근에 게시되었는데(글 작성 시점 기준 24시간 미만), 공식 문서에서 이에 대한 언급을 찾지 못했습니다.
궁금한 사항은 다음과 같습니다:
프로덕션 환경에서 이 이미지를 안전하게 사용할 수 있는지 확인하고 싶습니다.
감사합니다.
I believe the Docker image is discourse/base - Docker Image. (5M+ downloads vs 800+) See:
https://github.com/discourse/discourse_docker
The Docker repository will always contain the latest built version at: discourse/base - Docker Image, you should not need to build the base image.
Thanks for your reply, I know that. But I couldn’t get that discourse/base image to run easily with Docker Compose. This new discourse/discourse image makes setup much simpler and just works fine, but I want to understand its purpose and whether I can use it in production.
Take a read of:
discourse/discourse is new, but still experimental, so I wouldn’t recommend using it in production. We’ll certainly publish more info if/when that changes, and it’s ready for use.
As of right now, the only method we can support is the standard install.
As described, the Supported way to self-host is to follow the standard install. If you don’t want to do that then you’re sort-of on your own. If you want to launch with docker-compose, what I recommend is to use launcher to build your image, push it to a repo of your own and then use `./launcher start-cmd web_only’ to get the necessary ENV variables and such to launch it. And you’ll still need to do something to see that the database is migrated, assets precompiled, and so on.
You can also contrive to get github to build images for you and have them migrate and so on when launched (as will one day be provided by CDCK, it seems). I’ve done this for clients in the past. (Happy to help if you have a budget.)
If you like to live on the edge, you’re probably pretty safe using the “experimental” version with the caveat that you’ll need to have a staging site where you test each new deployment before pushing it to production and being prepared to either need to wait a while and/or do something that requires deep knowledge of discourse to move forward. A worst case (probably) is that you’d need to be prepared to make a backup and restore to a standard install until the experimental thing is ready for prime time.
Do you have an estimated release date or timeline for when discourse/discourse might be considered stable/production-ready?
Additionally, I would like to confirm: Is the discourse/discourse Docker image open source, and if so, could you provide the GitHub repository link?
I don’t have any timeline/guarantees right now. But hopefully we’ll have more info to share in the next few weeks.
Yes it’s all open source. It’s built & published regularly by this github actions workflow: discourse_docker/.github/workflows/push-web-only.yml at main · discourse/discourse_docker · GitHub
Thanks for the info and for sharing the GitHub link, much appreciated!
Yeah, it’s becoming an open secret of what’s in the oven 
You can get a technical preview of what’s upcoming, but like David said we can’t support it officially yet. There are tons of docs to plan, edge cases to test, etc… so we can’t recommend it for production until we smooth those things out.
@david / @featheredtoast, you guys and the rest of the team have done a great job here.
I just switched to discourse/discourse from bitnami/discourse for automated testing and it’s working great. Obviously my use case is perfect - spin up a new forum, run tests, delete.
So, just wanted to give a big thanks. I’m sure a lot of others will benefit from this too especially once it becomes stable / official / supported.
Similar situation, was looking for a quick way to spin up Discourse in a Docker Compose setup to make it easier for developers to build an SSO integration. This appears to work a treat (setup below for those who are interested):
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
Looking forward to hearing about future plans or timelines, would love to be able to run this in something like Digital Ocean App Platform (something that clients could manage with less technical know-how).
Ah thanks for sharing, @JackNZ . I didn’t even notice the discourse/postgres image 
I’ll have to fix that. Nevertheless, I’ll share where I’m at too. Maybe more interesting is the start.sh script here that, while in need of some cleanup, will create an admin user, API key, and disable rate limiters.
bitnami/discourse 관련 정보를 알려주셔서 정말 감사합니다. 제한된 네트워크 환경에서는 공식 방법으로 설치하는 것이 꽤 힘들었습니다. bitnami/discourse 이미지를 사용해 보겠습니다. 감사합니다!
도움이 필요할 경우를 대비한 힌트입니다.
Bitnami는 더 이상 해당 항목을 지원하지 않습니다. Upcoming changes to the Bitnami catalog (effective August 28th, 2025) · Issue #35164 · bitnami/charts · GitHub
아직 지원되지 않는 스탠드얼론 Discourse 이미지를 사용해 볼 것을 권합니다. 잘 작동한다는 보고를 여러 번 본 적이 있습니다.
discourse/discourse를 시도해 보겠습니다. 좋은 조언을 해 주셔서 감사합니다.
지금 프로덕션 배포에 거의 준비된 상태인가요? 아직 아니라면, 언제 배포될지에 대한 로드맵이나 예상 일정이 있을까요?
그리고 잘 만들었습니다. 이미지 태그를 간단히 업데이트하면 새 릴리스를 관리하는 것이 훨씬 쉬워지겠네요 
호스팅 환경에서 내부 업데이트가 진행 중인데, 예상치 못한 의존성 문제가 발생했습니다. 공식 지원으로 마킹하기 위해 배포하려면 먼저 이 문제들을 해결해야 하지만, 여기에서 남은 마지막 장애물들은 이번 분기 내에 해결될 것으로 예상합니다. 긴 시간이 걸렸네요.
그동안 제가 호스팅하는 모든 사이트는 discourse/discourse 도커 이미지를 통해 구축되어 있으며, 여기서는 잘 작동하고 있습니다.
@featheredtoast! 여기에서의 작업에 감사드립니다! discourse/discourse 이미지로 추가 플러그인을 설치할 수 있을까요? 그 과정은 어떻게 되나요?