A comfy UI for Hashicorp Vault.

Find a file

Kitteh 57a0ab5abe Add gitattributes.		2021-05-08 01:47:51 +01:00
.github/workflows	Change license filename.	2021-04-15 13:28:58 +01:00
screenshots	Add screenshots to readme.	2021-05-05 18:28:05 +01:00
src	Add typing to PwGen.ts.	2021-05-08 01:45:35 +01:00
.babelrc	Switch to eslint.	2021-04-18 10:42:57 +01:00
.eslintrc.json	Add typing to QRScanner.ts.	2021-05-08 00:54:50 +01:00
.gitattributes	Add gitattributes.	2021-05-08 01:47:51 +01:00
.gitignore	Initial Commit.	2021-04-15 13:01:58 +01:00
checkTranslations.mjs	Print language name in checkTranslations script.	2021-05-05 21:15:50 +01:00
LICENSE.md	Initial Commit.	2021-04-15 13:01:58 +01:00
package.json	Add typing to PageState.ts.	2021-05-07 23:08:02 +01:00
readme.md	Unbreak the markdown.	2021-05-05 18:29:35 +01:00
runLinter.sh	Add typing to PageState.ts.	2021-05-07 23:08:02 +01:00
tsconfig.json	Add typing to playground.ts.	2021-05-07 23:26:33 +01:00
webpack.config.js	Start work on adding typescript to codebase.	2021-05-07 22:23:52 +01:00

VaultUI

This is a very simple UI for working with secrets in Hashicorp Vault

How to build:

npm install --save-dev
npx webpack

The resulting built files will be in dist/

Use whatever browser you want, I personally test on latest Microsoft Edge Dev build.

npm install --save-dev
WEBPACK_MODE=development BROWSER=google-chrome npx webpack serve

Make sure to keep the order of comments and tags in the translation files src/translations the same.

When you want to PR an update, title it "Changed wording in..." or "Synced translations in de" or something along those lines.

To get a list of what languages need what translations added, run node ./checkTranslations.mjs Example:

Language: fr
Missing:  unseal_input_btn, unseal_qr_btn

Means those two missing things need to be added to french.

We don't yet support generate: true TOTP secrets but probably will in the future.