github/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2026-04-15 01:41:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix various typos (#835)

Browse Source
This commit is contained in:
Johan Van de Wauw
2022-03-09 01:44:08 +01:00
committed by GitHub
parent e178b7b4b2
commit 8fa2a5efe4
9 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/20-usage/71-project-settings.md
View File

@@ -24,7 +24,7 @@ If you set your project to trusted, a pipeline step and by this the underlying c
:::note
Only server admins can set this option. If you are not a server admin this option wont be shown in your project settings.
Only server admins can set this option. If you are not a server admin this option won't be shown in your project settings.
:::

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

@@ -76,9 +76,9 @@ services:
To handle sensitive data in docker-compose or docker-swarm configurations there are several options:
For docker-compose you can use a .env file next to your compose condfiguration to store the secrets outside of the compose file. While this seperates configuration from secrets it is still not very secure.
For docker-compose you can use a .env file next to your compose condfiguration to store the secrets outside of the compose file. While this separates configuration from secrets it is still not very secure.
Alternatively use docker-secrets. As it may be difficult to use docker secrets for environment variables woodpecker allows to read sensible data from files by profiding a `*_FILE` option of all sensible configuration variables. Woodpecker will try to read the value directly from this file. Keep in mind that when the original environment varibale gets specified at the same time it will override the value read from the file.
Alternatively use docker-secrets. As it may be difficult to use docker secrets for environment variables woodpecker allows to read sensible data from files by providing a `*_FILE` option of all sensible configuration variables. Woodpecker will try to read the value directly from this file. Keep in mind that when the original environment variable gets specified at the same time it will override the value read from the file.
```diff
# docker-compose.yml

2
docs/docs/30-administration/15-agent-config.md
View File

@@ -1,6 +1,6 @@
# Agent configuration
Agents are configured by the command line or environement variables. At the minimum you need the following information:
Agents are configured by the command line or environment variables. At the minimum you need the following information:
```yaml
# docker-compose.yml

2
docs/docs/92-development/06-guides.md
View File

@@ -32,5 +32,5 @@ Adding new properties to models will be handled automatically by the underlying
You should not use `sess.Begin()`, `sess.Commit()` or `sess.Close()` inside a migration. Session / transaction handling will be done by the underlying migration manager.
:::
To automatically execute the migration after the start of the server, the new migration needs to be added to the end of `migrationTasks` in `server/store/datastore/migration/migration.go`. After a successful execution of that transaction the server will automatically add the migration to a list, so it wont be executed again on the next start.
To automatically execute the migration after the start of the server, the new migration needs to be added to the end of `migrationTasks` in `server/store/datastore/migration/migration.go`. After a successful execution of that transaction the server will automatically add the migration to a list, so it won't be executed again on the next start.