trustchain-oc1-orchestral
/
authentik
Archived
10
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

website/docs: terminology clear unneeded sentence. (#2577) 

certificates: minor improvements
This commit is contained in:
Andre Mainka 2022-03-23 17:38:36 +01:00 committed by GitHub
parent 8e028c2feb
commit 0c53650216
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/core/certificates.md
View File

@ -39,7 +39,7 @@ You can also bind mount single files into the folder, as long as they fall under
Otherwise it will be imported as certificate. Otherwise it will be imported as certificate.
- If the file is called `fullchain.pem` or `privkey.pem` (the output naming of certbot), they will get the name of the parent folder. - If the file is called `fullchain.pem` or `privkey.pem` (the output naming of certbot), they will get the name of the parent folder.
- Files can be in any arbitrary file structure, and can have extension. - Files can be in any arbitrary file structure, and can have any extension.
- If the path contains `archive`, the files will be ignored (to better support certbot setups). - If the path contains `archive`, the files will be ignored (to better support certbot setups).
``` ```
@ -47,10 +47,10 @@ certs/
├── baz ├── baz
│   └── bar.baz │   └── bar.baz
│   ├── fullchain.pem │   ├── fullchain.pem
│   └── privkey.key │   └── privkey.pem
├── foo.bar ├── foo.bar
│   ├── fullchain.pem │   ├── fullchain.pem
│   └── privkey.key │   └── privkey.pem
├── foo.key ├── foo.key
└── foo.pem └── foo.pem
``` ```

4
website/docs/core/terminology.md
View File

@ -44,8 +44,6 @@ See [Property Mappings](./property-mappings/)
### Outpost ### Outpost
An outpost is a separate component of authentik, which can be deployed anywhere, regardless of the authentik deployment. The outpost offers services that aren't implemented directly into the authentik core, like Reverse Proxying. An outpost is a separate component of authentik, which can be deployed anywhere, regardless of the authentik deployment. The outpost offers services that aren't implemented directly into the authentik core, e.g. Reverse Proxying.
Currently there is only a reverse-proxy outpost, in the future there will be more different outpost types.
See [Outposts](./outposts/) See [Outposts](./outposts/)