36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
# Profiles and Databases
|
|
|
|
## Profiles
|
|
|
|
Every setting in OpsLog is **per-profile**: station identity, CAT, lookup, QSL
|
|
defaults, awards display, antennas, and which logbook to use. Create one profile
|
|
per callsign / station / event.
|
|
|
|
Switch or manage profiles in Settings. The active profile decides which logbook
|
|
your QSOs go to.
|
|
|
|
## Config vs. logbook — two different stores
|
|
|
|
| Store | What | Where |
|
|
|-------|------|-------|
|
|
| **Config** | settings, profiles, rigs/antennas, cluster nodes, lookup cache, award lists, QSL templates | always the **local SQLite** file under `data/` |
|
|
| **Logbook** | your QSOs | where the active profile points — local SQLite **or** shared MySQL |
|
|
|
|
Keeping config local means the UI is instant even when the logbook is a far-away
|
|
MySQL server.
|
|
|
|
## Shared MySQL logbook (multi-operator)
|
|
|
|
Point a profile's logbook at a **MySQL** database so several operators run **one
|
|
log** — e.g. a multi-op special-event call. Configure the host / database /
|
|
credentials in the profile's database settings.
|
|
|
|
This is also what powers [[Multi-Operator Live Status]] (each instance heartbeats
|
|
its activity into a `live_status` table).
|
|
|
|
## Backups
|
|
|
|
Optional **database + ADIF backup at shutdown** (Settings → Backup). Regardless,
|
|
copying the `data/` folder backs up your config and local logbook. See
|
|
[[Settings and Data]].
|