Docker as an alternative

For Linux environments there is a Dockerfile along with a docker-compose.yml: port 8086 → 8080 in the container, running as non-root, with a built-in health check on /health.

This is the route when no Windows server is available — a standalone Linux installation package does not currently exist.

Four volumes are mandatory

Without them the persistent data sits inside the container, and a up --build discards it:

Volume	Content
/app/data	the database, invoice files, each tenant’s templates
/app/keys	API keys (hashes)
/app/usage	the usage log
/app/.aspnet	the DataProtection key ring

/app/.aspnet in particular is easily forgotten

Without that key ring, all form tokens become invalid after every restart — and with them all sign-in sessions. The fault looks like an intermittent sign-in problem.

Add /app/logs to taste.

The settings come as environment variables

Under the scheme InvoiceApi__…. For Enterprise operation this includes:

environment:
  - InvoiceApi__Deployment__Mode=OnPremise
  - InvoiceApi__PublicBaseUrl=https://rechnung.firma.de

The build context

The context must cover the shared parent folder of both repositories

The project references to the PDF libraries point into a second repository, and what is not in the context, Docker cannot see. The head of the Dockerfile states the correct invocation.

This falls away once those libraries are available as packages.

What applies in the container as well

• libicu must be in the image — without ICU the process does not start; see System requirements
• the notes under Data and backup apply correspondingly to the volumes
• behind an upstream proxy, additionally Running behind a reverse proxy