- Create AGENTS.md to document project structure, commands, and conventions for AI agents.
- Implement Gitea workflow for automated Debian package builds (MySQL, SQLite) and release creation.
💘 Generated with Crush
Assisted-by: Gemini 2.5 Flash via Crush <crush@charm.land>
Vaultwarden 1.35.0+ needs OpenSSL 3.0, but Bullseye has only 1.1.
- Improve Dockerfile version replacement regex
- Enable vendored_openssl for Bullseye to statically link OpenSSL 3.0
- Add build dependencies (make, perl) for OpenSSL compilation
The runtime image was not the last stage thus it was always build and
left as untagged image. We can improve that. Refer to the docs for the
`docker build --target` option:
> Commands after the target stage will be skipped.
Ref: https://docs.docker.com/engine/reference/commandline/build/#specifying-target-build-stage---target
This commit simply moves the dpkg build stage patch above the runtime
image stage.
* 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.
* Set the newest upstream version as default
Instead of hardcoding the default version the latest upstream release should be used.
* Add curl as dependency
The shipped systemd-unit contains default values that could give the users a hard time starting the service. This warning should make things more clear.
* Add argument for database type
The optional argument "-d" allows to customize the database type.
* Modify patch to work with all db types
* Add database type to filename
* Add dynamic modification of systemd-unit
Dynamically changes the systemd-unit to require the appropriate database service.
sko
Nico Isenbeck