Windows service deployment¶
Use this path only when your environment requires a Windows-hosted API instead of the container deployment model.
What is packaged¶
Release artifacts include:
- published API binaries for
win-x64 - PowerShell install and uninstall scripts from
deploy/windows-service
Installation flow¶
- download the Windows service zip from a release
- extract it on the target host
- run the provided install script with the intended service account
- provide configuration for database connectivity, proxy behavior, and certificates
- start the service and verify health
Runtime considerations¶
A Windows service deployment still needs the same production inputs as the container path:
- PostgreSQL connection string
- OpenIddict signing and encryption material
- management web hosting strategy or reverse proxy plan
- log collection and service recovery policy
Validation checklist¶
Confirm:
- the service starts cleanly
/healthand/aliverespond through the host or reverse proxy path- token issuance works with the configured certificates
- the management web can still reach the API authority you published
If your environment supports containers, the Kubernetes or container path is usually easier to operate and upgrade.