From 08ee9ee44c0692fe7c7c2eb82c21d601afd241d9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Fischer?= Date: Fri, 11 Apr 2025 08:54:33 +0200 Subject: [PATCH] chore(docs): Fix links in docs --- README.md | 6 +++--- docs/architecture.md | 4 ++-- docs/development.md | 2 +- docs/getting-started.md | 5 ++++- docs/security.md | 2 +- docs/workflow.md | 14 +++++++------- 6 files changed, 18 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index 04f33c1b..6e688142 100644 --- a/README.md +++ b/README.md @@ -96,7 +96,7 @@ Find out more about the permission system in the[roles & permissions concept](./ All technical releases are created using [Semantic Versioning](https://semver.org/lang/de/). Gitlab provides an -[overview on the releases](https://gitlab.opencode.de/bmi/opendesk/deployment/sovereign-workplace/-/releases) +[overview on the releases](https://gitlab.opencode.de/bmi/opendesk/deployment/opendesk/-/releases) of this project. Please find a list of the artifacts related to the release either in the source code archive attached to the release or @@ -115,8 +115,8 @@ More information about different data storages used within openDesk are describe We love to get feedback from you! -Related to the deployment / contents of this repository, -please use the [issues within this project](https://gitlab.opencode.de/bmi/opendesk/deployment/sovereign-workplace/-/issues). +For feedback related to the deployment / contents of this repository, +please use the [issues within this project](https://gitlab.opencode.de/bmi/opendesk/deployment/opendesk/-/issues). If you want to address other topics, please check the section ["Rückmeldungen und Beteiligung" in the OVERVIEW.md](https://gitlab.opencode.de/bmi/opendesk/info/-/blob/main/OVERVIEW.md#rückmeldungen-und-beteiligung) of the [openDesk Info Repository](https://gitlab.opencode.de/bmi/opendesk/info). diff --git a/docs/architecture.md b/docs/architecture.md index b6829028..e8f12152 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -237,7 +237,7 @@ The [OX SOAP API](https://oxpedia.org/wiki/index.php?title=Open-Xchange_Provisio - (Managed) Resources - Users -To find out more, see [Roles & Permissions](permissions.md). +To find out more, see [Roles & Permissions](./docs/permissions.md). ## SCIM @@ -381,7 +381,7 @@ The end user focussed components are called applications and provide the functio Other components are of type "Service", these are used for development and evaluation purposes only, they need to be replaced in production deployments. -For the APIs / Protocols supported by the applications, please read the [apis.md](./architecture/apis.md). +For the APIs / Protocols supported by the applications, please read the [apis.md](./docs/architecture/apis.md). ## Collabora (Office) diff --git a/docs/development.md b/docs/development.md index 37786319..924fcd0e 100644 --- a/docs/development.md +++ b/docs/development.md @@ -60,7 +60,7 @@ Before you investigate any app-specific configuration, it is recommended that yo The `main` branch is configured to be the default branch, as visitors of the project on Open CoDE should see that branch by default. -Please use the `develop` branch to diverge your branch(es) from. See the [workflow guide](./workflow.md) +Please use the `develop` branch to diverge your branch(es) from. See the [workflow guide](./docs/workflow.md) for more details on naming conventions. There is a CI bot that automatically creates a merge request once you initially push your branch to Open CoDE. diff --git a/docs/getting-started.md b/docs/getting-started.md index 6f1d4470..628808d5 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -230,6 +230,9 @@ ingress: ingressClassName: "name-of-my-nginx-ingress" ``` +Currently, the only supported ingress controller is `ingress-nginx` (see +[requirements.md](./docs/requirements.md)) for reference). + ### Container runtime Some apps require specific configurations for the container runtime. You can set your container runtime like `cri-o`, @@ -263,7 +266,7 @@ cluster: ## Customize deployment -While openDesk configures the applications with meaningful defaults, you can check [functional.md](functional.md) if you want to change these defaults to better match your use case. +While openDesk configures the applications with meaningful defaults, you can check [functional.md](./docs/functional.md) if you want to change these defaults to better match your use case. ## Connectivity diff --git a/docs/security.md b/docs/security.md index 71e050d1..e99c9e56 100644 --- a/docs/security.md +++ b/docs/security.md @@ -29,7 +29,7 @@ All charts except the ones mentioned below are verifiable: This list gives you an overview of default security settings and whether they comply with security standards: -⟶ Visit our generated detailed [Security Context](./security-context.md) overview. +⟶ Visit our generated detailed [Security Context](./docs/security-context.md) overview. # NetworkPolicies diff --git a/docs/workflow.md b/docs/workflow.md index 1ed93040..b3aa69d2 100644 --- a/docs/workflow.md +++ b/docs/workflow.md @@ -121,7 +121,7 @@ classDiagram The focus of openDesk is to provide an integrated functional productivity platform based on the involved suppliers' functional components (products). These functional components usually rely on specific service components, e.g. database services for persistence. When running openDesk in production, the operator is responsible for providing these services in production-grade. For evaluation and development purposes, the openDesk deployment automation includes these services. -Find the list of functional and service components in the [deployment automation's components.md](https://gitlab.opencode.de/bmi/opendesk/deployment/sovereign-workplace/-/blob/main/docs/components.md). +Find the list of functional and service components in the [archictecture documentation](./docs/architecture.md). ## Origins @@ -146,7 +146,7 @@ openDesk uses Apache 2.0 as the license for their work. A typical reuse copyrigh # SPDX-FileCopyrightText: 2025 Zentrum für Digitale Souveränität der Öffentlichen Verwaltung (ZenDiS) GmbH # SPDX-License-Identifier: Apache-2.0 ``` -The way to mark the license header as a comment differs between the various file types. Please find matching examples for all types across the [deployment automation repository](https://gitlab.opencode.de/bmi/souveraener_arbeitsplatz/deployment/sovereign-workplace). +The way to mark the license header as a comment differs between the various file types. Please find matching examples for all types across the [deployment automation repository](https://gitlab.opencode.de/bmi/opendesk/deployment/opendesk). > **Note**
> If a `SPDX-FileCopyrightText` already exists with the copyright owner described above but with an past year (e.g. 2024), please update this copyright header line to cover (up to and including) the current year, e.g. `2024-2025`. @@ -238,7 +238,7 @@ The Standard Quality Gate addresses quality assurance steps that should be execu 1. Linting - Blocking - Licensing: [reuse](https://github.com/fsfe/reuse-tool) - - openDesk specific: Especially `images.yaml.gotmpl` and `charts.yaml.gotmpl`, find more details in [development.md](./development.md). + - openDesk specific: Especially `images.yaml.gotmpl` and `charts.yaml.gotmpl`, find more details in [development.md](./docs/development.md). - Non-Blocking - Security: [Kyverno policy check](../.kyverno) addressing some IT-Grundschutz requirements - Formal: Yaml @@ -370,14 +370,14 @@ Commit messages must adhere to the [Conventional Commit standard](https://www.co Example: `fix(open-xchange): Bump to 8.26 to heal issue with functional mailbox provisioning.` > **Note**
-> The commit messages are an essential part of the [technical releases](https://gitlab.opencode.de/bmi/opendesk/deployment/sovereign-workplace/-/releases) as the release's notes are generated from the messages. +> The commit messages are an essential part of the [technical releases](https://gitlab.opencode.de/bmi/opendesk/deployment/opendesk/-/releases) as the release's notes are generated from the messages. #### Verified commits We only allow verified commits; please read on about the options you have to make your commits verified: -- https://docs.gitlab.com/ee/user/project/repository/ssh_signed_commits/ -- https://docs.gitlab.com/ee/user/project/repository/gpg_signed_commits/ -- https://docs.gitlab.com/ee/user/project/repository/x509_signed_commits/ +- https://docs.gitlab.com/user/project/repository/signed_commits/ssh/ +- https://docs.gitlab.com/user/project/repository/signed_commits/gpg/ +- https://docs.gitlab.com/user/project/repository/signed_commits/x509/ # Footnotes