Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions .github/workflows/build.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -36,12 +36,6 @@ jobs:
- extract-version
steps:
- uses: actions/checkout@v2
- name: 'Replace environment tokens'
uses: cschleiden/replace-tokens@v1
with:
files: '["**/environment.prod.ts"]'
env:
TOKEN_APPLICATION_VERSION: "${{ needs.extract-version.outputs.turnierplan_version }}"
- name: Login to container registry
uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
with:
Expand Down
5 changes: 1 addition & 4 deletions docker/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,8 @@ Currently, there exists one Dockerfile with the `dotnet/aspnet:10.0-alpine` base
docker build -t turnierplan:dev -f docker/turnierplan-amd64/Dockerfile .
```

The resulting container image can be run as described in the [main readme](../README.md). The following minimal example uses an in-memory data store and does not mount any volumes:
The resulting container image can be run as described in the [installation guide](https://docs.turnierplan.net/installation/#container-image). The following minimal example uses an in-memory data store and does not mount any volumes:

```shell
docker run -p 80:8080 -e Turnierplan__ApplicationUrl="http://localhost" -e Database__InMemory="true" turnierplan:dev
```

> [!WARNING]
> Manually built container images should not be used in production! This is because the relevant GitHub workflow performs other important steps before actually building the images.
6 changes: 2 additions & 4 deletions docs/pages/installation/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Für die Installation auf einem lokalen Rechner oder einer VM kann im einfachste
```yaml
services:
turnierplan.database:
image: postgres:latest
image: postgres:18
environment:
- POSTGRES_PASSWORD=P@ssw0rd
- POSTGRES_DB=turnierplan
Expand All @@ -40,7 +40,7 @@ services:
restart: unless-stopped

turnierplan.application:
image: ghcr.io/turnierplan-net/turnierplan:latest
image: ghcr.io/turnierplan-net/turnierplan:2026.2.0
depends_on:
- turnierplan.database
environment:
Expand All @@ -62,8 +62,6 @@ networks:
turnierplan:
```

Statt dem `latest`-Tag sollte immer eine spezifische Version für die Images der Datenbank und von turnierplan.NET verwendet werden. Dies ermöglicht eine bessere Kontrolle, welche Updates wann eingespielt werden. Die neuste Version ist auf der [Release-Seite](https://github.com/turnierplan-NET/turnierplan.NET/releases) der Repository auffindbar.

Die URL, welche letztendlich für den Zugriff auf turnierplan.NET verwendet wird, sollte in der Umgebungsvariable `Turnierplan__ApplicationUrl` spezifiziert werden. Falls bspw. eine Domain `example.com` verwendet wird, sollte der Wert der Umgebungsvariable `https://example.com` sein. Falls turnierplan.NET im lokalen Netzwerk gehostet wird, könnte der Wert bspw. `http://192.168.0.187` sein. Es muss natürlich das korrekte Protokoll (HTTP vs. HTTPS) verwendet werden.

Die Volume-Mounts sind im [nachfolgenden Abschnitt](#volume-mounts) näher beschrieben. Je nach Konfiguration kann das Volume-Mount vom turnierlpan.NET-Container auch überflüssig sein.
Expand Down
39 changes: 39 additions & 0 deletions misc/bump-version.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
#!/bin/bash

#
# Bumps the turnierplan.NET version in all relevant files for the next release.
#
# Usage:
# ./bump-version.sh <new version>
#

if (( $# != 1 )); then
echo "Usage: $0 <new version>"
exit 1
fi

# The 'version.xml' file is considered leading
current_version=$(grep -Po '\d+\.\d+\.\d+' ../src/version.xml)

next_version="$1"
if [[ ! $next_version =~ ^20[2-9][0-9]+\.[1-9][0-9]*\.[0-9]+$ ]]; then
echo "Error: The specified new version '$1' is not a valid version."
exit 1
fi

if [[ $current_version == $next_version ]]; then
echo "Error: The current version is already '$1'."
exit 1
fi

echo "Bumping version: '$current_version' -> '$next_version'"

update_file () {
echo "Updating file: $1"
sed -i -e "s/${current_version//./\\.}/$next_version/g" "../$1"
}

update_file "src/version.xml"
update_file "src/Turnierplan.App/Client/package.json"
update_file "src/Turnierplan.App/Client/src/environments/environment.prod.ts"
update_file "docs/pages/installation/index.md"
2 changes: 1 addition & 1 deletion src/Turnierplan.App/Client/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "turnierplan-net",
"version": "0.0.0",
"version": "2026.2.0",
"description": "The client application of turnierplan.NET",
"private": true,
"license": "AGPL-3.0-only",
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
export const environment = {
production: true,
defaultTitle: 'turnierplan.NET',
version: '#{TOKEN_APPLICATION_VERSION}#',
version: '2026.2.0',
originOverwrite: undefined,
includeE2EData: false,
doUpdatesCheck: true
Expand Down
Loading