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
Merge changes from #131 and #133.
Co-authored-by: Stefan Melmuk <stefan.melmuk@gmail.com>
Co-authored-by: GeekCornerGH <45696571+GeekCornerGH@users.noreply.github.com>
As requested in #122 moved all the image files into a correct directory structure.
This does seem a bit logical indeed. And it makes it more clear where
which replaced image goes. It also makes the `cp` command less error prone.
Fixes#122
- Updated actions to the latest version
- Added support for ghcr.io, same as on the vaultwarden repo.
Don't forget the add the `GHCR_REPO` and `DOCKERHUB_REPO` to the correct locations.
I did not add quay.io here, since i do not think it really is needed for
this repo. Once this is merged and working fine, we could change the
`FROM` in the Dockerfile at the vaultwarden repo.
