Add HaVeWa 0.3.0 - #6040
Open
fgilde wants to merge 2 commits into
Open
Add HaVeWa 0.3.0#6040fgilde wants to merge 2 commits into
fgilde wants to merge 2 commits into
Conversation
added 2 commits
September 1, 2026 16:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HaVeWa 0.3.0
Property-management software for rental and HOA (WEG, the German form of condominium ownership)
administration, with its own PostgreSQL. Properties, units, people and meters; leases with stepped
and index rent and deposits; charges, payments, open items, SEPA mandates and dunning;
service-charge statements with a BetrKV allocation engine; co-ownership shares, economic plan, HOA
fees, annual statement and reserves; owners' meetings with agenda, voting and the resolution
collection; documents; maintenance tickets with workflow and time tracking; tenant and owner
portals; camt.053 import and DATEV/SEPA export. Multi-tenant, role-based, bilingual (German and
English), with a REST API and an MCP server so an agent works under the same permissions a person
has.
ghcr.io/fgilde/hausverwaltung:sha-53d22ce(
sha256:5d0388c8bc288bbd95ca0ad9d8ed09de451bbfa29db71b6daa4a5ff2fb9cec0c) andpostgres:16.10-alpine— both manifest lists withlinux/amd64andlinux/arm64, publicPackage
Two services behind
app_proxy(port: 3210→ container3000): the app and its PostgreSQL. Bothbind-mount under
${APP_DATA_DIR}/data—storagefor documents and generated statements,dbforthe database. No host paths, no Docker socket, no privileged mode, no capabilities, no raw published
ports, no dependencies.
exports.shderives two independent secrets withderive_entropy: the session secret that signs thelogins and the database password. Keeping them apart is the point — one value for both would tie a
session forgery to a database compromise.
Credentials
None. The first visit opens a setup wizard that creates the administrator and the management
company, so
defaultUsernameanddefaultPasswordare empty. The app can also seed a demo data setwith a known login, and this package deliberately does not.
Testing
npm run lint:apps -- havewa --check-images: clean.docker buildx imagetools inspecton both pinned digests listslinux/amd64andlinux/arm64.The arm64 image is new: the project's CI builds each architecture on a runner of that architecture
and merges the digests, because
next buildunder emulation does not finish in a CI run.postgres:16.10-alpinewere started together with exactly this environment, networkand volume layout: the schema migrates on first start (43 tables), the app answers on the mapped
port, the setup page appears rather than a login with default credentials, and a restart against
the same volumes keeps the data.
Screenshots and logo
Logo: https://raw.githubusercontent.com/fgilde/hausverwaltung/main/icon.png