Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Docs: fix broken docker links #16716

Merged
merged 1 commit into from
Sep 12, 2024
Merged

Docs: fix broken docker links #16716

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion docs/installation-and-operations/installation/kubernetes/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,6 @@ sidebar_navigation:
# Kubernetes

Kubernetes is a container orchestration tool. As such it can use the
OpenProject docker container in the same manner as shown in the [docker section](../docker/#one-container-per-process-recommended).
OpenProject docker container in the same manner as shown in the [docker section](../docker/).

In the [openproject-deploy](https://github.com/opf/openproject-deploy/blob/stable/14/kubernetes/README.md) repository we provide further information and an exemplary set of YAML files defining a complete OpenProject setup on Kubernetes.
2 changes: 1 addition & 1 deletion docs/installation-and-operations/installation/synology/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar_navigation: false
# Synology

Synology offers NAS devices that come with a UI for starting docker containers on them.
This means OpenProject has to be used exactly as described in the [docker](../docker/#one-container-per-process-recommended) section.
This means OpenProject has to be used exactly as described in the [docker](../docker/) section.

## Launching the container

Expand Down
2 changes: 1 addition & 1 deletion docs/installation-and-operations/misc/migration-to-postgresql13/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ sudo yum remove pgsql10

## Compose-based docker installation

> Please follow this section only if you have installed OpenProject using [this procedure](../../installation/docker/#one-container-per-process-recommended).
> Please follow this section only if you have installed OpenProject using [this procedure](../../installation/docker/).
> Before attempting the upgrade, please ensure you have performed a backup of your installation by following the [backup guide](../../operation/backing-up/).

You can find the upgrade instructions for your docker-compose setup in the [openproject-deploy](https://github.com/opf/openproject-deploy/blob/stable/14/compose/control/README.md#upgrade) repository.
Expand Down
2 changes: 1 addition & 1 deletion docs/installation-and-operations/operation/restoring/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,7 @@ You may need to create the `files` directory if it doesn't exist yet.

#### 4) Start OpenProject

Start the container as described in the [installation section](../../installation/docker/#one-container-per-process-recommended)
Start the container as described in the [installation section](../../installation/docker/)
mounting `/var/lib/openproject/pgdata` (and `/var/lib/openproject/assets/` for attachments).

## Changing the database schema from cloud to on-premises
Expand Down
2 changes: 1 addition & 1 deletion docs/installation-and-operations/operation/upgrading/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,7 +159,7 @@ sudo chown -R 102 /volume1/openproject/*
```

After that it's simply a matter of launching the new container mounted with the copied `pgdata` and `assets` folders
as described in the [installation section](../../installation/docker/#one-container-per-process-recommended).
as described in the [installation section](../../installation/docker/).

## Upgrade notes from 9.x

Expand Down
1 change: 1 addition & 0 deletions script/docs/check_links
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,7 @@ class DocsChecker
@docs.push(
{ path: "#{@root_path}/api/v3/spec.json", anchors: [], links: [] },
{ path: "#{@root_path}/api/v3/spec.yml", anchors: [], links: [] },
{ path: "#{@root_path}/installation-and-operations/installation/docker-compose", anchors: [], links: [] },
{ path: "#{@root_path}/installation-and-operations/installation/helm-chart", anchors: [], links: [] },
{ path: "#{@root_path}/development/translate-openproject/fair-language", anchors: [], links: [] }
)
Expand Down