Service type
App service
App service
Discourse service
Self-hosted Discourse forum service built from application source, with linked PostgreSQL, Redis, and outbound email.
Use it as a versioned stack building block that can build from source, plug into CI/CD, and connect to external providers without hardcoding secrets into the codebase.
Why teams use this service
Technical profile
Review versions, ports, source, and packaging.
Stacks that use it
See where this service fits in ready-made stacks.
Source builds and CI/CD
Start from a compatible boilerplate, use Wodby CI, and publish images cleanly.
Backups and data import
Move working data between environments with storage-backed workflows.
Runtime wiring and defaults
See ports, links, storage, configs, and runtime behavior.
Overview
Technical profile and packaging
This page shows how Discourse is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.
Versions
2026.10, 2026.8, 2026.7
Source repository
Public Helm chart
Ports and protocols
80/HTTP
Labels
discourse, forum
Persistent volumes
Discourse shared data
Stacks
Use it inside ready-made stacks or your own
These public stacks already include Discourse as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.
CI/CD
Build from source and ship changes without extra glue work
Discourse can build from source as part of a stack. Start from a compatible public boilerplate or connect your repository and keep CI/CD and image storage inside the same Wodby workflow.
Discourse stable
Start from a working boilerplate instead of wiring the build process from scratch.
discourse/discourseDiscourse ESR
Start from a working boilerplate instead of wiring the build process from scratch.
discourse/discourseGit providers
Connect repositories from supported Git providers when this service should build from your own codebase.
CI providers
Wodby CI is the default path, but external CI providers can fit the same build and release workflow when that suits your team better.
Container registries
Keep built images in Wodby Registry by default or store them in another registry without changing how the service is built.
Keep secrets and variables outside the codebase
Attach provider credentials and environment variables at the platform level so the build and runtime do not depend on hardcoded secrets.
Data workflows
Keep recovery points ready and move data between environments
Discourse supports backup workflows, so teams can keep recovery points available and move archives into external storage without rebuilding the process per environment.
Attach backups to the service model
Keep scheduled backup behavior with the same versioned service definition instead of rebuilding it environment by environment.
Upload archives to cloud storage
Send backup archives to external storage providers instead of keeping them only inside the platform.
Runtime wiring
Reuse connectivity, storage, and runtime defaults
This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.
Endpoints
80/HTTP
Technical domains
HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.
Volumes
Discourse shared data
Settings
2 settings can be overridden per environment.
Service links
These links define which other services can connect to Discourse when it is used inside a stack.
db
Eligible linked services
redis
Eligible linked services
sendmail
Eligible linked services