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.
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.
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
