.github/workflows/docker-image.yml

@@ -6,7 +6,18 @@ on:
 jobs:
   lint-test:
     name: lint, build & test
-    uses: './.github/workflows/lint-test.yml'
+    runs-on: ubuntu-latest
+    steps:
+    - name: checkout
+      uses: actions/checkout@v3
+    - name: setup Node
+      uses: actions/setup-node@v3
+      with:
+        node-version: 18.x
+    - run: npm ci
+    - run: npm run lint
+    - run: npm run build
+    - run: npm test
 
   build-and-publish:
     name: build & publish Docker image
@@ -14,13 +25,13 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: check out the repo
-        uses: actions/checkout@v4
+        uses: actions/checkout@v3
       - name: set up QEMU
         uses: docker/setup-qemu-action@v3
       - name: configure Docker to use buildx
-        uses: docker/setup-buildx-action@v3
+        uses: docker/setup-buildx-action@v2
       - name: log in to Docker Hub
-        uses: docker/login-action@v3
+        uses: docker/login-action@v2
         with:
           username: ${{ secrets.DOCKER_USERNAME }}
           password: ${{ secrets.DOCKER_ACCESS_TOKEN }}
@@ -39,7 +50,7 @@ jobs:
 
       # this is for the public-transport/infrastructure cluster
       - name: log in to GitHub Container Registry
-        uses: docker/login-action@v3
+        uses: docker/login-action@v2
         with:
           registry: ghcr.io
           username: ${{ github.repository_owner }}

.github/workflows/lint-test.yml

@@ -1,35 +0,0 @@
-name: lint, build & test
-on:
-  push:
-    branches:
-      - '*'
-  pull_request:
-    branches:
-      - '*'
-  workflow_call:
-
-jobs:
-  lint-test:
-    name: lint, build & test
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        node-version:
-          - '16.x'
-          - '18.x'
-          - '20.x'
-          - '22.x'
-
-    steps:
-    - name: checkout
-      uses: actions/checkout@v4
-    - name: setup Node
-      uses: actions/setup-node@v4
-      with:
-        node-version: ${{ matrix.node-version }}
-
-    - run: npm ci
-
-    - run: npm run lint
-    - run: npm run build
-    - run: npm test

docs/readme.md

@@ -4,21 +4,17 @@
 
 [![API status](https://badgen.net/uptime-robot/status/m793274556-25c5e9bbab0297d91cda7134)](https://stats.uptimerobot.com/57wNLs39M/793274556)
 
-Because it wraps [an API](https://github.com/public-transport/hafas-client/blob/6/readme.md#background) of [Deutsche Bahn](https://de.wikipedia.org/wiki/Deutsche_Bahn), it **includes most of the long-distance and regional traffic, as well as some international trains and local buses**. Essentially, it returns whatever data the [*DB Navigator* app](https://www.bahn.de/p/view/service/mobile/db-navigator.shtml) shows*, **including realtime delays and disruptions**.
-
-*When comparing results from this API to what the DB Navigator app shows there might be occasional differences due to them utilizing different, not 100% identical backends.*
+Because it wraps [an API](https://github.com/public-transport/hafas-client/blob/6/readme.md#background) of [Deutsche Bahn](https://de.wikipedia.org/wiki/Deutsche_Bahn), it **includes most of the long-distance and regional traffic, as well as some international trains and local buses**. Essentially, it returns whatever data the [*DB Navigator* app](https://www.bahn.de/p/view/service/mobile/db-navigator.shtml) shows, **including realtime delays and disruptions**.
 
 - [Getting Started](getting-started.md)
-- [API documentation](api.md) (run `npm run build` to generate)
-- [OpenAPI playground with API documentation](https://petstore.swagger.io/?url=https%3A%2F%2Fv6.db.transport.rest%2F.well-known%2Fservice-desc%0A)
+- [API documentation](api.md)
+- [OpenAPI playground](https://petstore.swagger.io/?url=https%3A%2F%2Fv6.db.transport.rest%2F.well-known%2Fservice-desc%0A)
 
 ## Why use this API?
 
 ### Realtime Data
 
-This API returns realtime data whenever it is upstream. The [API for DB's mobile app](https://github.com/public-transport/hafas-client/blob/6/p/db/readme.md) provides it.
-
-*Note: Different endpoints might remove realtime data like delays and cancellations at different times, i.e. after a journey's arrival.*
+This API returns realtime data whenever its upstream, the [API for DB's mobile app](https://github.com/public-transport/hafas-client/blob/6/p/db/readme.md), provides it.
 
 ### No API Key
 

package.json

@@ -2,7 +2,7 @@
 	"private": true,
 	"name": "db-rest",
 	"description": "A clean REST API wrapping around the Deutsche Bahn API.",
-	"version": "6.0.5",
+	"version": "6.0.4",
 	"type": "module",
 	"bin": {
 		"db-rest": "./index.js"

readme.md

@@ -15,16 +15,14 @@
 
 ## installing & running
 
-### access to Redis
-
-It is recommended that you let `bvg-rest` cache HAFAS responses within a [Redis](https://redis.io/) cache. To use this feature, set `$REDIS_URL` (e.g. to `redis://localhost:6379/1` when running Redis locally).
+`db-rest` expects a [Redis](https://redis.io/) server running on `127.0.0.1:6379` (default port), but you can set the `REDIS_URL` environment variable to change this.
 
 ### via Docker
 
-A Docker image [is available as `docker.io/derhuerst/db-rest:6`](https://hub.docker.com/r/docker.io/derhuerst/db-rest:6).
+A Docker image [is available as `derhuerst/db-rest:6`](https://hub.docker.com/r/derhuerst/db-rest:6).
 
 ```shell
-docker run -d -p 3000:3000 docker.io/derhuerst/db-rest:6
+docker run -d -p 3000:3000 derhuerst/db-rest:6
 ```
 
 *Note:* The Docker image does not contain the Redis server.