Some misc changes.
- Moved old patch files to a `legacy` sub-folder
- If a legacy patch is used, show a warning and pause for 10 seconds
- Updated the checkout and Dockerfile so both use the same way of
cloning the Bitwarden/client repo
- Updated the `patch_web_vault.sh` script to try and detect the vault version
- Added two new make commands to prepare and release a new version
- Added a `.env` feature for the `Makefile` to set some defaults
Mainly used for using either `docker` or `podman` and for the GitHub
Release script to have a predefined GPG user/key
currently it fails (because it can't resolve the $tailwindcss reference)
but also in general we might not want to depend on automatic updating the
dependencies without checking them first.
in web-v2023.8.x the pageTitle (i.e. "$APP_NAME Web Vault") was removed,
so instead of using the hardcoded replacement, we replace the name of
the project `Vaultwarden Web`
the footer is changed again from v2023.7.1 for better legibility.
compared to the previous patch files some changes are purely cosmetic due
to running prettier and eslint.
and we don't need to change or pack the 404.html file since Vaultwarden
already provides a 404 page
All the scripts used by this repo were more focused on Linux based systems.
They did not work on macOS or other BSD based systems because of flags
or commands which are not available.
This PR resolves those items by adjusting the failed commands so they
work on both Linux and macOS/BSD systems.
Fixes#112
- Updated web-vault to v2023.1.1
- Added a small patch to allow scrolling the organizations menu when
there are a lot of organizations.
Fixes https://github.com/dani-garcia/vaultwarden/issues/3148
I also created a PR at bitwarden/clients, pending approval.
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.
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
The patch is almost identical just some offsets are different.
This version does solve the multiple `/sync` requests which will benefit
the loading time and load on the server!
- Added support for v2.26.1
- Hide some more input fields we do not use
- Fixed building with npm (The audit fix breaks the build)
- Fixed the vaultwarden version json filename.
There needs to be a small change on the vaultwarden server for this to
be fully supported as far as i could tell.
So maybe not yet ready for merge/tagging.
