Skip to content

dionysius/vaultwarden-web-vault-deb

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

81 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

deb packaging for vaultwarden web vault

This debian source package builds vaultwarden-web-vault natively on your build environment from the official upstream enriched with the vaultwarden patches. 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.

You will also need vaultwarden-deb.

Download prebuilt packages

Prebuild deb and src packages are automatically built in Github Actions for the latest Ubuntu LTS and Debian stable in various architectures (if applicable).

For manual installation they are available in the releases section and you can verify the signatures with this signing-key.

For using apt they are available on packagecloud. See their installation instructions on how to setup the apt source. Be aware that they use a different signing key. vaultwarden-deb is also automatically uploaded to this repo.

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)
  • If nodejs/npm is not recent enough
    • Don't forget to look into your *-updates/*-backports apt sources for newer versions
    • Use a package from nodesource
    • This debian source also supports those installed with help of nvm
      • Requires preloaded nvm use <version> before invoking packaging

Packaging

  • Clone with git-buildpackage: gbp clone https://github.com/dionysius/vaultwarden-web-vault-deb.git
  • Switch to the folder: cd vaultwarden-web-vault-deb
  • Build with git-buildpackage: gbp 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)

TODOs

  • Automatic notification on new upstream releases. Optimally with automatic PR with those updates