From c81c50daa428f539898d693da1c3bb2ef149f71d Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Sat, 17 Feb 2024 11:40:29 +0100 Subject: [PATCH] admin: installation: v1.21 is current --- docs/admin/installation-binary.md | 2 +- docs/admin/installation-docker.md | 16 ++++++++-------- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/admin/installation-binary.md b/docs/admin/installation-binary.md index 097c736e..ef31de7c 100644 --- a/docs/admin/installation-binary.md +++ b/docs/admin/installation-binary.md @@ -16,7 +16,7 @@ and make it executable: > **NOTE:** when a line starts with #, it means the command 'foo --bar' must be run as root (or with sudo). -`# cp forgejo-1.20.5-0-linux-amd64 /usr/local/bin/forgejo` +`# cp forgejo-1.21.5-0-linux-amd64 /usr/local/bin/forgejo` `# chmod 755 /usr/local/bin/forgejo` Make sure `git` and `git-lfs` are installed: diff --git a/docs/admin/installation-docker.md b/docs/admin/installation-docker.md index 0c36ba72..c463dd78 100644 --- a/docs/admin/installation-docker.md +++ b/docs/admin/installation-docker.md @@ -6,12 +6,12 @@ license: 'CC-BY-SA-4.0' Forgejo provides [container images](https://codeberg.org/forgejo/-/packages/container/forgejo/versions) for use with Docker or other containerization tools. ```shell -docker pull codeberg.org/forgejo/forgejo:1.20.5-0 +docker pull codeberg.org/forgejo/forgejo:1.21.5-0 ``` -The **1.20** tag is set to be the latest patch release, starting with **1.20.1-0**. The **1.20** tag will then be equal to **1.20.2-0** when it is released and so on. +The **1.21** tag is set to be the latest patch release, starting with **1.21.1-0**. The **1.21** tag will then be equal to **1.21.2-0** when it is released and so on. -Upgrading from **1.X** to **1.X+1** (for instance from **1.19** to **1.20**) requires a [manual operation and human verification](../upgrade/). However it is possible to use the **X.Y** tag (for instance **1.20**) to get the latest point release automatically. +Upgrading from **1.X** to **1.X+1** (for instance from **1.20** to **1.21**) requires a [manual operation and human verification](../upgrade/). However it is possible to use the **X.Y** tag (for instance **1.21**) to get the latest point release automatically. Here is a sample [docker-compose](https://docs.docker.com/compose/install/) file: @@ -24,7 +24,7 @@ networks: services: server: - image: codeberg.org/forgejo/forgejo:1.20 + image: codeberg.org/forgejo/forgejo:1.21 container_name: forgejo environment: - USER_UID=1000 @@ -84,7 +84,7 @@ networks: services: server: - image: codeberg.org/forgejo/forgejo:1.20 + image: codeberg.org/forgejo/forgejo:1.21 container_name: forgejo environment: - USER_UID=1000 @@ -132,7 +132,7 @@ networks: services: server: - image: codeberg.org/forgejo/forgejo:1.20 + image: codeberg.org/forgejo/forgejo:1.21 container_name: forgejo environment: - USER_UID=1000 @@ -232,8 +232,8 @@ networks: services: server: -- image: codeberg.org/forgejo/forgejo:1.20 -+ image: codeberg.org/forgejo/forgejo:1.20-rootless +- image: codeberg.org/forgejo/forgejo:1.21 ++ image: codeberg.org/forgejo/forgejo:1.21-rootless container_name: forgejo environment: + - USER_UID=1024