# Installation

OpsLog is a single Windows executable — no installer, no runtime to add. Pure Go
+ an embedded WebView2 (present on Windows 10/11 by default).

## Download and run

1. Grab the latest `OpsLog.exe` from the project's **Releases** page.
2. Put it in its own folder (it will create a `data/` folder next to itself).
3. Double-click to run. On first launch you pick a **language** (English /
   French) and OpsLog creates its local database.

> **Where is my data?** A `data/` folder is created next to the executable,
> holding the SQLite config + local logbook, QSL templates, recordings and
> backups. Keep the exe and `data/` together, or back up `data/`. See
> [[Settings and Data]].

## Building from source (developers)

OpsLog is built with **Wails v2.11**.

```bash
# Dev — Vite hot-reload; Go methods reachable at http://localhost:34115
wails dev

# Production build → build/bin/OpsLog.exe
wails build

# Regenerate Go↔TS bindings after changing exported App methods
wails generate module
```

Prerequisites: Go, Node.js, and the Wails CLI (`~/go/bin/wails.exe`). No CGO /
C toolchain is needed.

## First-run checklist

- **Settings → General** — language, theme, and the two Main-view panes.
- **Settings → Station** — your callsign, grid, name (used for lookups, awards,
  QSL cards and the map).
- **Settings → CAT** — connect your radio ([[CAT Control]]).
- **Settings → Lookup** — QRZ.com / HamQTH credentials for callsign lookup.

Continue with **[[Getting Started]]**.
