github/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2025-09-26 11:29:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix links in documentation (#832)

Browse Source
This commit is contained in:
mscherer
2022-03-04 09:16:21 +01:00
committed by GitHub
parent 90dcc77870
commit 32d56ed795
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/20-usage/25-multi-pipeline.md
View File

@@ -17,7 +17,7 @@ The Multi-Pipeline feature allows the pipeline to be split into several files an
## Example multi-pipeline definition ## Example multi-pipeline definition
:::warning :::warning
Please note that files are only shared between steps of the same pipeline (see [File changes are incremental](/docs/usage/pipeline-syntax#file-changes-are-incremental)). That means you cannot access artifacts e.g. from the `build` pipeline below in the `deploy` pipeline. Please note that files are only shared between steps of the same pipeline (see [File changes are incremental](/docs/usage/pipeline-syntax#file-changes-are-incremental)). That means you cannot access artifacts e.g. from the `build` pipeline below in the `deploy` pipeline.
If you still need to pass artifacts between the pipelines you need use storage [plugins](docs/usage/plugins/plugins) (e.g. one which stores files in an Amazon S3 bucket). If you still need to pass artifacts between the pipelines you need use storage [plugins](/docs/usage/plugins/plugins) (e.g. one which stores files in an Amazon S3 bucket).
::: :::
```bash ```bash

6
docs/docs/30-administration/10-server-config.md
View File

@@ -4,7 +4,7 @@
Registration is closed by default. While disabled an administrator needs to add new users manually (exp. `woodpecker-cli user add`). Registration is closed by default. While disabled an administrator needs to add new users manually (exp. `woodpecker-cli user add`).
If registration is open every user with an account at the configured [SCM](docs/administration/vcs/overview) can login to Woodpecker. If registration is open every user with an account at the configured [SCM](/docs/administration/vcs/overview) can login to Woodpecker.
This example enables open registration for users that are members of approved organizations: This example enables open registration for users that are members of approved organizations:
```diff ```diff
@@ -338,12 +338,12 @@ Example: `WOODPECKER_LIMIT_CPU_SET=1,2`
### `WOODPECKER_CONFIG_SERVICE_ENDPOINT` ### `WOODPECKER_CONFIG_SERVICE_ENDPOINT`
> Default: `` > Default: ``
Specify a configuration service endpoint, see [Configuration Extension](docs/administration/external-configuration-api) Specify a configuration service endpoint, see [Configuration Extension](/docs/administration/external-configuration-api)
### `WOODPECKER_CONFIG_SERVICE_SECRET` ### `WOODPECKER_CONFIG_SERVICE_SECRET`
> Default: `` > Default: ``
Specify a signing secret for the configuration service endpoint, see [Configuration Extension](docs/administration/external-configuration-api) Specify a signing secret for the configuration service endpoint, see [Configuration Extension](/docs/administration/external-configuration-api)
### `WOODPECKER_CONFIG_SERVICE_SECRET_FILE` ### `WOODPECKER_CONFIG_SERVICE_SECRET_FILE`
> Default: `` > Default: ``