TownlightTownlight Beta 1

Townlight Windows beta support

These instructions cover the signed Windows x64 public beta 1.7.2.1.

Download the current Windows MSI · Release and checksums · Suite manual · Public beta announcement

Installation and recovery

Use a fresh installation/profile. This MSI does not upgrade an existing legacy profile. Follow the first-run instructions and backup, recovery and maintenance guidance. Preserve existing data and backups. Do not rename or delete the compatibility profile directory %LOCALAPPDATA%\CivicSuite to work around a setup problem.

Verify the downloaded MSI against the release checksums and check its Authenticode signature is Valid, with signer Scott Converse. Use the exact release link here; GitHub's Latest download now resolves to this public beta. The acceptance summary describes the installed checks and their limits. Local-model acceptance used a 16 GiB Sandbox; an 8 GiB run timed out without saving a draft.

For setup problems, consult troubleshooting before filing an installer issue. Do not remove a database or existing profile as a troubleshooting shortcut.

Where to report a problem

Area Issue tracker
Installer, first run, desktop shell, documentation or cross-product workflow Townlight Suite
Shared identity, permissions, audit or platform services Core
Public records Records
Meetings, agendas, votes or minutes Meetings
Municipal code, proposals or adoption Code
Accessibility reviews, drafts or exports Access
Notice review, approval, proof or archive Notice
Zoning Zoning
Planning Planning
Permitting Permitting
Inspections Inspections
Station capture or media handoff Station

If you cannot identify the owning product, start with the Suite issue tracker. For questions and evaluation feedback, use Townlight Discussions.

What to include

  • Installed version (1.7.2.1) and Windows version.
  • The selected products/profile and whether this was a fresh installation.
  • Steps to reproduce, what you expected and what happened.
  • Redacted error messages, logs or screenshots, using synthetic data where possible.

Do not attach resident information, credentials, tokens, database copies or unredacted backups to public issues. Do not post security vulnerabilities in public issues: follow the security policy and report privately to the affected repository.

Separate deployments and evidence

The resident portal requires separate deployment. The Windows installer does not provision a public website. Standalone CivicCast remains a separate product. The current Windows acceptance uses synthetic data and does not establish a live city deployment or physical broadcast acceptance. Follow each product guide for its supported workflow.