public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[bitnami/discourse] Release 2026.4.0-debian-12-r3 (#92480) 

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-04-15 16:24:22 +02:00 committed by GitHub
parent cc91dac4aa
commit 3b95a99d3d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 12 additions and 89 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
bitnami/discourse/2026/debian-12/Dockerfile
View File

@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-08T21:52:08Z" \
org.opencontainers.image.created="2026-04-15T12:53:29Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/discourse/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/discourse" \
@ -27,9 +27,9 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"python-3.12.13-3-linux-${OS_ARCH}-debian-12" \
"python-3.12.13-7-linux-${OS_ARCH}-debian-12" \
"wait-for-port-1.0.10-9-linux-${OS_ARCH}-debian-12" \
"ruby-3.4.9-0-linux-${OS_ARCH}-debian-12" \
"ruby-3.4.9-1-linux-${OS_ARCH}-debian-12" \
"postgresql-client-18.3.0-0-linux-${OS_ARCH}-debian-12" \
"node-20.20.2-0-linux-${OS_ARCH}-debian-12" \
"brotli-1.2.0-0-linux-${OS_ARCH}-debian-12" \
@ -54,7 +54,7 @@ COPY rootfs /
RUN /opt/bitnami/scripts/discourse/postunpack.sh
ENV APP_VERSION="2026.4.0" \
BITNAMI_APP_NAME="discourse" \
IMAGE_REVISION="2" \
IMAGE_REVISION="3" \
LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \
PATH="/opt/bitnami/python/bin:/opt/bitnami/common/bin:/opt/bitnami/ruby/bin:/opt/bitnami/postgresql/bin:/opt/bitnami/node/bin:/opt/bitnami/brotli/bin:$PATH"

93
bitnami/discourse/README.md
View File

@ -11,7 +11,13 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name discourse bitnami/discourse:latest
```
**Warning**: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the [Environment Variables](#environment-variables) section for a more secure deployment.
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/discourse/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/discourse/docker-compose.yml)
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/discourse).
## Why use Bitnami Secure Images?
@ -42,24 +48,6 @@ The Bitnami Discourse&reg; Docker image is only available to [Bitnami Secure Ima
Discourse requires access to a PostgreSQL database to store information. We'll use the [Bitnami Docker Image for PostgreSQL](https://github.com/bitnami/containers/tree/main/bitnami/postgresql) for the database requirements.
### Run the application using Docker Compose
```console
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/discourse/docker-compose.yml > docker-compose.yml
docker-compose up -d
```
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/discourse).
### Troubleshooting discourse
If you need to run discourse administrative commands like [Create admin account from console](https://meta.discourse.org/t/create-admin-account-from-console/17274), you can do so by executing a shell inside the container and running with the proper environment variables.
```console
cd /opt/bitnami/discourse
RAILS_ENV=production bundle exec rake admin:create
```
## Persisting your application
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
@ -145,8 +133,6 @@ The following tables list the main variables you can set.
| `DISCOURSE_DEFAULT_DATABASE_HOST` | Default database server host. | `postgresql` |
| `DISCOURSE_DEFAULT_REDIS_HOST` | Default Redis(R) server host. | `redis` |
When you start the Discourse image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line.
#### Examples
##### SMTP configuration
@ -165,70 +151,7 @@ The Bitnami Discourse&reg; Docker image from the [Bitnami Secure Images](https:/
## Logging
The Bitnami Discourse Docker image sends the container logs to `stdout`. To view the logs:
```console
docker logs discourse
```
Or using Docker Compose:
```console
docker-compose logs discourse
```
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Maintenance
### Backing up your container
To backup your data, configuration and logs, follow these simple steps:
#### Step 1: Stop the currently running container
```console
docker stop discourse
```
Or using Docker Compose:
```console
docker-compose stop discourse
```
#### Step 2: Run the backup command
We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
```console
docker run --rm -v /path/to/discourse-backups:/backups --volumes-from discourse busybox \
cp -a /bitnami/discourse /backups/latest
```
### Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the PostgreSQL database container:
```diff
$ docker run -d --name postgresql \
...
- --volume /path/to/postgresql-persistence:/bitnami/postgresql \
+ --volume /path/to/postgresql-backups/latest:/bitnami/postgresql \
bitnami/postgresql:latest
```
For the Discourse container:
```diff
$ docker run -d --name discourse \
...
- --volume /path/to/discourse-persistence:/bitnami/discourse \
+ --volume /path/to/discourse-backups/latest:/bitnami/discourse \
bitnami/discourse:latest
```
The Bitnami Discourse&reg; Docker image sends the container logs to the `stdout`. You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Notable Changes