bbohard
/
bitwarden_rs-debian
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
bitwarden_rs-debian/README.md

37 lines
1.1 KiB
Markdown
Raw Normal View History

Add a readme
2019-03-26 18:44:01 +01:00
# Bitwarden_rs debian package helper
[Bitwarden_rs](https://github.com/dani-garcia/bitwarden_rs) is an "Unofficial Bitwarden compatible server written in Rust".
Fix typo
2019-03-27 10:39:12 +01:00
This repository will help you produce a debian package.
Add a readme
2019-03-26 18:44:01 +01:00
## TL;DR
Make sure you have the required build dependencies:
* docker
* git
Do not duplicate Dockerfile The packaging Dockerfile will be generated by patching the one in bitwarden_rs sources.
2019-03-27 10:19:46 +01:00
* patch
Fetch the newest upstream version from github api (#17) * Set the newest upstream version as default Instead of hardcoding the default version the latest upstream release should be used. * Add curl as dependency
2020-06-27 14:45:48 +02:00
* curl
Add a readme
2019-03-26 18:44:01 +01:00
Then:
```
git clone https://github.com/greizgh/bitwarden_rs-debian.git
cd bitwarden_rs-debian
Support for arm32v7 (#25) * Move Dockerfile.patch files to architecture dependent directories Need a way to distinguish between patches when we implement support for other architectures. Putting them in different paths seems simple and straight forward enough. * Add -a option to support arm32v7 and amd64 architectures Previous releases lacked support for compiling for arm32v7 architecture. In order to keep previous behaviour the default is set to amd64. Using the -a option, users can now choose between arm32v7 and amd64. If arm32v7 is used only the Buster release of debian is supported. The limitation is due to the libmariadb3:armhf dependency not being avaliable in earlier debian releases. * Update documentation to detail the -a option * Remove reference to local dirs * Set debian package to report correct architecture for arm32v7 build * Format arm32v7 Dockerfile.patch to match the amd64 * Handle architecture property in control file dynamically Similar to version, the architecture property in the control file should be handled dynamically. The build script will now replace the architecture prop from control.dist to match the choosen architecture.
2020-11-10 11:08:37 +01:00
./build.sh -r 1.17.0
Add support for different Debian versions (#8)
2019-12-02 22:32:28 +01:00
```
The `build.sh` script will build bitwarden_rs for the same Debian version which targets bitwarden_rs.
Support for arm32v7 (#25) * Move Dockerfile.patch files to architecture dependent directories Need a way to distinguish between patches when we implement support for other architectures. Putting them in different paths seems simple and straight forward enough. * Add -a option to support arm32v7 and amd64 architectures Previous releases lacked support for compiling for arm32v7 architecture. In order to keep previous behaviour the default is set to amd64. Using the -a option, users can now choose between arm32v7 and amd64. If arm32v7 is used only the Buster release of debian is supported. The limitation is due to the libmariadb3:armhf dependency not being avaliable in earlier debian releases. * Update documentation to detail the -a option * Remove reference to local dirs * Set debian package to report correct architecture for arm32v7 build * Format arm32v7 Dockerfile.patch to match the amd64 * Handle architecture property in control file dynamically Similar to version, the architecture property in the control file should be handled dynamically. The build script will now replace the architecture prop from control.dist to match the choosen architecture.
2020-11-10 11:08:37 +01:00
To compile for a different Debian version, specify the release name (e.g. Stretch, Buster) using the `-o` option. You can compile for arm32v7 or amd64 architecture using the `-a` option, only the Buster (default) release of debian is supported by arm32v7.
Add support for different Debian versions (#8)
2019-12-02 22:32:28 +01:00
```
./build.sh -o stretch
Add a readme
2019-03-26 18:44:01 +01:00
```
Add post installation section
2019-03-26 19:00:42 +01:00
## Post installation
The packaged systemd unit is **disabled**, you need to configure bitwarden_rs through its
[EnvFile](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Command%20lines):
`/etc/bitwarden_rs/config.env`
You will also probably want to setup a reverse proxy.