Vaultwarden web vault deb packages

Easy to install and highly configurable debian packages for running Vaultwarden on your system natively without docker.

Installation

Head over to vaultwarden-deb for installation instructions as this repository contains the debian source for building the web vault part.

Alternatively, download prebuilt packages from the releases section and verify signatures with the signing-key. Packages are automatically built in Github Actions. You will also need vaultwarden-deb.

Release schedule

This project packages the web UI for vaultwarden-deb. Releases are automatically coordinated with the main vaultwarden package, which release state dictate the release state of the web vault package.

Build source package

This debian source package builds Vaultwarden Web Vault natively on your build environment. No annoying docker! It is managed with git-buildpackage and aims to be a pretty good quality debian source package. You can find the maintaining command summary in debian/gbp.conf.

Requirements

Installed git-buildpackage from your apt

Installed build dependencies as defined in debian/control Build-Depends (will notify you in the build process otherwise). mk-build-deps can help you automate the installation, for example:

mk-build-deps -i -r debian/control -t "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends --yes"

If nodejs/npm is not recent enough don't forget to look into your *-updates/*-backports apt sources for newer versions or use a package from nodesource

Build package

Clone with git-buildpackage and switch to the folder:

gbp clone https://github.com/dionysius/vaultwarden-web-vault-deb.git
cd vaultwarden-web-vault-deb

Build with git-buildpackage - there are many arguments to fine-tune the build (see gbp buildpackage --help and dpkg-buildpackage --help), notable options: -b (binary-only, no source files), -us (unsigned source package), -uc (unsigned .buildinfo and .changes file), --git-export-dir=<somedir> (before building the package export the source there), for example:

gbp buildpackage -b -us -uc

On successful build packages can now be found in the parent directory ls ../*.deb.