paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 47 Packages Projects Releases Wiki Activity

docs: follow up on PR: #32844 where update the database getting-started docker example to newest version

Browse Source 
Signed-off-by: Linus Andersson <sunil.andersson@gmail.com>
This commit is contained in:
Linus Andersson
2026-02-14 11:28:49 +01:00
parent cdb4719e08
commit 363eac721c
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started/config/database.md
+4 -4
View File
@@ -208,16 +208,16 @@ You may not want to install Postgres locally, the following sections outline alt
You can run Postgres in a Docker container, this is great for local development or getting a Backstage POC up and running quickly, here's how:
First we need to pull down the container image, we'll use Postgres 17, check out the [Postgres Version Policy](../../overview/versioning-policy.md#postgresql-releases) to learn which versions are supported.
First we need to pull down the container image, we'll use Postgres 18, check out the [Postgres Version Policy](../../overview/versioning-policy.md#postgresql-releases) to learn which versions are supported.
```shell
docker pull postgres:17-bookworm
docker pull postgres:18-trixie
```
Then we just need to start up the container.
```shell
docker run -d --name postgres --restart=always -p 5432:5432 -e POSTGRES_PASSWORD=<secret> postgres:17-bookworm
docker run -d --name postgres --restart=always -p 5432:5432 -e POSTGRES_PASSWORD=<secret> postgres:18-trixie
```
This will run Postgres in the background for you, but remember to start it up again when you reboot your system.
@@ -229,7 +229,7 @@ Another way to run Postgres is to use Docker Compose, here's what that would loo
```yaml title="docker-compose.local.yaml"
services:
postgres:
image: postgres:17-bookworm
image: postgres:18-trixie
environment:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: <secret>
docs/overview/versioning-policy.md
+1 -1
View File
@@ -195,4 +195,4 @@ The Backstage project recommends and supports using PostgreSQL for persistent st
The PostgreSQL [versioning policy](https://www.postgresql.org/support/versioning/) is to release a new major version every year with new features which is then supported for 5 years after its initial release.
Our policy mirrors the PostgreSQL versioning policy - we will support the last 5 major versions. We will also test the newest and oldest versions in that range. For example, if the range we support is currently 13 to 17, then we would only test 13 and 17 explicitly.
Our policy mirrors the PostgreSQL versioning policy - we will support the last 5 major versions. We will also test the newest and oldest versions in that range. For example, if the range we support is currently 14 to 18, then we would only test 14 and 18 explicitly.