docs(README): migrate from docker.io to git.cryptic.systems

.gitea/workflows/markdown-linters.yaml

@@ -1,46 +0,0 @@
-name: Markdown linter
-
-on:
-  pull_request:
-    paths: [ "**/*.md" ]
-    types: [ "opened", "reopened", "synchronize" ]
-  push:
-    branches:
-    - '**'
-    paths: [ "**/*.md" ]
-    tags-ignore:
-    - '**'
-  workflow_dispatch: {}
-
-jobs:
-  markdown-link-checker:
-    container:
-      image: docker.io/library/node:23.11.0-alpine
-    runs-on:
-    - ubuntu-latest
-    steps:
-    - name: Install tooling
-      run: |
-        apk update
-        apk add git npm
-    - uses: actions/checkout@v4.2.2
-    - name: Verify links in markdown files
-      run: |
-        npm install
-        npm run readme:link
-
-  markdown-lint:
-    container:
-      image: docker.io/library/node:23.11.0-alpine
-    runs-on:
-    - ubuntu-latest
-    steps:
-    - name: Install tooling
-      run: |
-        apk update
-        apk add git
-    - uses: actions/checkout@v4.2.2
-    - name: Lint markdown files
-      run: |
-        npm install
-        npm run readme:lint

.markdownlint.yaml

@@ -56,8 +56,6 @@ MD013:
   tables: false
   # Include headings
   headings: true
-  # Include headings
-  headers: true
   # Strict length checking
   strict: false
   # Stern length checking
@@ -70,11 +68,6 @@ MD022:
   # Blank lines below heading
   lines_below: 1
 
-# MD024/no-duplicate-heading/no-duplicate-header - Multiple headings with the same content
-MD024:
-  # Only check sibling headings
-  allow_different_nesting: true
-
 # MD025/single-title/single-h1 - Multiple top-level headings in the same document
 MD025:
   # Heading level

Makefile

@@ -1,6 +1,6 @@
 # DC_VERSION
-# Only required to install a specifiy version
-DC_VERSION?=v2.35.0 # renovate: datasource=github-releases depName=docker/compose
+# Only required to install a specify version
+DC_VERSION?=v2.36.0 # renovate: datasource=github-releases depName=docker/compose
 
 # CONTAINER_RUNTIME
 # The CONTAINER_RUNTIME variable will be used to specified the path to a container runtime. This is needed to start and
@@ -34,7 +34,6 @@ container-image/build:
 PHONY:=container-image/delete
 container-image/delete:
 	- ${CONTAINER_RUNTIME} image rm ${DC_IMAGE_FULLY_QUALIFIED}
-	- ${CONTAINER_RUNTIME} image rm ${BASE_IMAGE_FULL}
 
 # PUSH CONTAINER IMAGE
 # =====================================================================================================================

README.md

@@ -2,9 +2,9 @@
 
 [![Docker Pulls](https://img.shields.io/docker/pulls/volkerraschek/docker-compose)](https://hub.docker.com/r/volkerraschek/docker-compose)
 
-This project contains all sources to build the container image `docker.io/volkerraschek/docker-compose`. The primary
-goal of this project is to package the binary `docker-compose` as container image. The source code of the binary can be
-found in the upstream project of [docker/compose](https://github.com/docker/compose).
+This project contains all sources to build the container image `git.cryptic.systems/volker.raschek/docker-compose`. The
+primary goal of this project is to package the binary `docker-compose` as container image. The source code of the binary
+can be found in the upstream project of [docker/compose](https://github.com/docker/compose).
 
 The workflow or how `docker-compose` can in general be used is documented [here](https://docs.docker.com/compose/).
 Nevertheless, here are some examples of how to use the container image.