currently if `builds/web-vault` exists the script will copy the newly
built web-vault to `builds/web-vault/web-vault`.
include suggestions from code review
Co-authored-by: BlackDex <black.dex@gmail.com>
This PR updates the web-vault to v2022.11.1
It also replaces the main logo and top left icon to indicate it is
Vaultwarden.
And the footer text has been change to `Vaultwarden (unofficial Bitwarden® server)`
This hopefully helps causing less confusion.
currently, if you built the web-vault the `node_modules` folder is
stashed which takes a long time. since this is an ignored folder and we
use `npm ci` to build the web-vault we don't really need to stash it.
`npm ci` will always start with a clean build anyway.
see https://docs.npmjs.com/cli/v8/commands/npm-ci
This version has a new feature which isn't supported yet by vaultwarden.
It shouln't be that hard to add this functionality i think.
You can now revoke and restore user access to an org.
- Updated to the latest released web-vault.
- Made some small changes to the checkout script to catch tags like
`2022.6.2` and `v2022.6.2` and convert them to `web-v2022.6.2` instead.
Updated the web-vault to the latest released version.
This version is also using the new repo `bitwarden/clients` instead of the old `bitwarden/web`.
All files have been changed where needed.
- Updated web-vault to v2022.05.0
- Made several changes to the build scripts for ease of building/patching etc...
You can now run `make checkout` to pull/update the repo to the wanted version
There is also a `make patch-web-vault` to patch the repo
A `make generate-patch` to create a patch file from the current changes
And many more changes
