Another Ham Radio Logbook -- Web, Multi-user multiple-logbook, with eQSL upload support
Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
Dashie der otter 5d668c653f
Bump urllib3 from 1.25.2 to 1.25.3 (#155)
2 mēnešus atpakaļ
.vscode Dev related 1 gadu atpakaļ
controllers ooops 9 mēnešus atpakaļ
migrations Fix all PEP8 and errors 9 mēnešus atpakaļ
static Add Fork-Awesome 9 mēnešus atpakaļ
templates Add missing flashed messages 9 mēnešus atpakaļ
tests Floats are a mistake 9 mēnešus atpakaļ
tmp Add gitkeep for tmp 3 gadus atpakaļ
uploads/pictures Add gitkeep 3 gadus atpakaļ
.coveragerc Add base files for the CI 9 mēnešus atpakaļ
.dockerignore Add base files for the CI 9 mēnešus atpakaļ
.drone.yml Update .drone.yml 4 mēnešus atpakaļ
.gitignore Make TODO public 9 mēnešus atpakaļ
.gitmodules I should commit more frequently. 3 gadus atpakaļ
.isort.cfg Add base files for the CI 9 mēnešus atpakaļ Add some more requirements 9 mēnešus atpakaļ Add missing flashed messages 9 mēnešus atpakaļ Meh 9 mēnešus atpakaļ Reformat files 9 mēnešus atpakaļ
babel.cfg Add base files for the CI 9 mēnešus atpakaļ gnagnagna 9 mēnešus atpakaļ Raise exceptions instead of return 9 mēnešus atpakaļ Encrypt password on db seed, closes #38 9 mēnešus atpakaļ Unused 9 mēnešus atpakaļ Fix all PEP8 and errors 9 mēnešus atpakaļ Fix all PEP8 and errors 9 mēnešus atpakaļ
pyproject.toml Fix all PEP8 and errors 9 mēnešus atpakaļ
requirements.txt Bump urllib3 from 1.25.2 to 1.25.3 2 mēnešus atpakaļ
setup.cfg Fix all PEP8 and errors 9 mēnešus atpakaļ Fix requirements in setup 9 mēnešus atpakaļ Reformat with Black 9 mēnešus atpakaļ Refactoring of to use the newer Flask CLI, also adapted for unittests 9 mēnešus atpakaļ

Another Ham Radio Log

Build Status

Versions requirement


Install a BDD (mysql is supported, SQLite maybe, PostgreSQL should be)
Makes sure that encoding is/will be in UNICODE/UTF-8
git clone
cd ahrl
git submodule init
git submodule update
pip3 install --requirement requirements.txt
export FLASK_ENV=<development or production>
$ create your postgresql database like "ahrl"
flask db upgrade
flask seed
flask cron update_dxcc_from_cty
flask run
Don't forget to update default Config by getting to "Your user" (top right) then "Config"

Creating an user

If you have enabled registration in config, the first user registered will be ADMIN !

Or if you have disabled registration, use the flask createuser command to create an user.

Production running

TODO: venv, systemd services, waitress

Default config

Crontabs and cache actions

List of cron target availables. Makes sure to run them under the user which runs ahrl and virtualenv if you use it. Commands:

  • python cron update_qsos_countries # Update all QSOs if missing a Country/DXCC entry by using ClubLog
  • python cron # List all available crons
  • python cache # Same for cache actions

Crons explained

  • update_qsos_countries Update QSOs which have an empty country
  • sync_to_eqsl Push to eQSL marked QSO with ‘Requested’
  • sync_from_eqsl Get from eQSL log to update QSOs eQSL state
  • update_dxcc_from_cty Update the database copy of this file
  • update_qsos_hamqth Update all QSOs with datas from HamQTH if needed

Crontabs example

# eQSL may cache the file to download so only fetch every four hours 
*/5 * * * * cd /where/is/ahrl ; python3 cron sync_to_eqsl
0 */4 * * * cd /where/is/ahrl ; python3 cron sync_from_eqsl


  • MIT License

Fork from

Random notes (since I am currently no licensed and then I am SWL at the moment)

  • Your user have a CALLSIGN, LOCATOR and IARU Zone
    • Each logbook can have a different LOCATOR or CALLSIGN
    • I see that more like to have a different logbook if you do SAT / GHZ / Portable / Mobile etc.
    • Or if you want to have a log for your home base, from some DX remote site, etc.
    • So the IARU Zone isn’t a choice for logbook, they use user profile anyway
  • Any things can be subject to discussion anyway, if something isn’t really ok, no problem to see what to do

How we handle DateTimes and timezones

  • DateTimes are stored in database without timezone, so we manage to always save them in UTC:

    time_off = db.Column(db.DateTime(timezone=False), default=None) time_on = db.Column(db.DateTime(timezone=False), default=None, index=True)

  • User input DateTime are first converted to a timezone-aware DateTime of ‘current_user.timezone’ (using pytz)

  • Then are converted .astimezone() to UTC, still with pytz and stored in database

  • The reverse, DB -> View are either:

    • Using a function (utils: dt_utc_to_user_tz(dt, user=None)) or jinja2 helper (localize, mapped to dt_utc…) to display the correct DateTime with the user offset/timezone
    • Converted to a timezone-aware DateTime of ‘UTC’ using pytz
    • Then converted .astimezone() to current_user.timezone with pytz (like qsos:edit part)

Dates notes

  • When entering a QSO format is : DD-MM-YYYY HH:MM:SSSS (Two fields)
  • A Python DateTime is “YYYY MM DD HH:MM:SS” (approximately, order is ok)
  • In ADIF format is YYYYMMDD HHMMSS (Two fields)
  • When editing a QSO, the unique field is displayed as “YYYY-MM-DD HH:MM:SS”

Modes and Submodes

  • They are based on ADIF ones (
  • ‘mode’ is like a category and ‘submode’ the real mode used (anyway…)
  • SSB is ‘category’ and in fact you use ‘USB’ or ‘LSB’
  • So in some places the keyword ‘mode’ is used but in fact it’s really ‘submode’ which is used


  • Radio/CAT edit, add you own rig and link them when QSOing


  • MIT License