mirror of
https://github.com/oauth2-proxy/oauth2-proxy.git
synced 2024-11-24 08:52:25 +02:00
0693856bc3
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> |
||
---|---|---|
.. | ||
docs | ||
src | ||
static | ||
versioned_docs | ||
versioned_sidebars | ||
.gitignore | ||
babel.config.js | ||
docusaurus.config.js | ||
package-lock.json | ||
package.json | ||
README.md | ||
sidebars.js | ||
versions.json |
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.