1
0
mirror of https://github.com/oauth2-proxy/oauth2-proxy.git synced 2024-11-24 08:52:25 +02:00
oauth2-proxy/docs
Jack Henschel 0693856bc3
Explicitly state precedence of config sources in docs (#1439)
I was recently looking into the order in which oauth2-proxy evaluates it configuration options from the various sources.
I think this will also be helpful for other users.
Since oauth2-proxy is using viper, the order of configuration sources is as follows [1]:
> Viper uses the following precedence order. Each item takes precedence over the item below it:
>
>    explicit call to Set
>    flag
>    env
>    config
>    key/value store
>    default

[1] https://github.com/spf13/viper/blob/master/README.md#why-viper

Co-authored-by: Joel Speed <Joel.speed@hotmail.co.uk>
2021-11-15 09:24:04 +00:00
..
docs Explicitly state precedence of config sources in docs (#1439) 2021-11-15 09:24:04 +00:00
src Migrate existing documentation to Docusaurus 2020-11-05 15:36:27 +00:00
static Migrate existing documentation to Docusaurus 2020-11-05 15:36:27 +00:00
versioned_docs Explicitly state precedence of config sources in docs (#1439) 2021-11-15 09:24:04 +00:00
versioned_sidebars Create versioned docs for release v7.2.x 2021-10-22 18:11:28 +01:00
.gitignore Migrate existing documentation to Docusaurus 2020-11-05 15:36:27 +00:00
babel.config.js Migrate existing documentation to Docusaurus 2020-11-05 15:36:27 +00:00
docusaurus.config.js Add version dropdown to docs header 2020-11-08 19:37:46 +00:00
package-lock.json Migrate existing documentation to Docusaurus 2020-11-05 15:36:27 +00:00
package.json Migrate existing documentation to Docusaurus 2020-11-05 15:36:27 +00:00
README.md Migrate existing documentation to Docusaurus 2020-11-05 15:36:27 +00:00
sidebars.js Deprecate GAP-Signature and add a warning on usage (#1103) 2021-03-14 09:47:44 -07:00
versions.json Create versioned docs for release v7.2.x 2021-10-22 18:11:28 +01:00

Website

This website is built using Docusaurus 2, a modern static website generator.

Installation

yarn install

Local Development

yarn start

This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server.

Build

yarn build

This command generates static content into the build directory and can be served using any static contents hosting service.

Deployment

GIT_USER=<Your GitHub username> USE_SSH=true yarn deploy

If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.