sheppy/opendesk
1
0
Fork 0
mirror of https://gitlab.opencode.de/bmi/opendesk/deployment/opendesk.git synced 2025-12-06 15:31:38 +01:00
Code Issues Packages Projects Releases Wiki Activity

chore(docs): Fix links in docs

Browse Source
This commit is contained in:
René Fischer
2025-04-11 08:54:33 +02:00
parent d444d24489
commit 91882b22e5
6 changed files with 16 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -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/).
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
@@ -116,7 +116,7 @@ More information about different data storages used within openDesk are describe
We love to get feedback from you!
For feedback 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).
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).

4
docs/architecture.md
View File

@@ -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)

3
docs/development.md
View File

@@ -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 to the project on openCode 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.
# External artifacts - `charts.yaml.gotmpl` and `images.yaml.gotmpl`
@@ -159,3 +159,4 @@ for Helm charts.
You may also want to make use of our [standard CI](https://gitlab.opencode.de/bmi/opendesk/tooling/gitlab-config) to
quickly get Helm charts and container images that are signed, linted, scanned, and released.
Check out the `.gitlab-ci.yaml` files in the project's [Charts](https://gitlab.opencode.de/bmi/opendesk/components/platform-development/charts) or [Images](https://gitlab.opencode.de/bmi/opendesk/components/platform-development/images) to get an idea just how little you need to do by yourself.
components

4
docs/getting-started.md
View File

@@ -231,7 +231,7 @@ ingress:
```
Currently, the only supported ingress controller is `ingress-nginx` (see
[requirements.md](requirements.md)) for reference).
[requirements.md](./docs/requirements.md)) for reference).
### Container runtime
@@ -266,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

2
docs/security.md
View File

@@ -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

14
docs/workflow.md
View File

@@ -121,7 +121,7 @@ classDiagram
The focus of openDesk is to provide an integrated and 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 production-grade services. 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**<br>
> If a `SPDX-FileCopyrightText` already exists with the copyright owner described above but with a 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**<br>
> 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 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