Go to file

Absenth 4253176fa1 Merge pull request #2 from absenth/absenth-patch-1 Update README.md		2023-09-18 17:08:48 -05:00
qsolink	Adding fastapi_versioning and setting up version v1_0 for all operations	2023-09-17 11:59:09 -05:00
tests	Trying to add pytest tests, largely unsuccessfully	2023-09-16 11:01:45 -05:00
.gitignore	Initial Commit - models defined, crud operations defined	2023-09-16 09:39:00 -05:00
LICENSE	Initial commit	2023-09-16 08:09:01 -05:00
README.md	Update README.md	2023-09-18 17:06:12 -05:00
poetry.lock	Adding fastapi_versioning and setting up version v1_0 for all operations	2023-09-17 11:59:09 -05:00
pyproject.toml	Adding fastapi_versioning and setting up version v1_0 for all operations	2023-09-17 11:59:09 -05:00

README.md

qsolink

JSON/REST based Ham Radio Logging Platform

QSO Link (pronounced Q S O Link), Named after the Ham Radio Q Codes, is intended to be a cross platform ham radio contact logging package. It comes from a series of frustrations over the many years I've been a ham, where replacing a computer resulted in lost log databases. Or needing to come up with solutions to sync logs when using a laptop and a desktop, and possibly even a phone depending on the context of how I was operating. My goal is to use a JSON/REST API server, that can be accessed through a number of different front ends.

Future goals will include writing a Terminal User Interface front end, inspired by Fabian Kurz, DJ5CW logging package yfklog. In addition to a GUI interface, inspired by N3FPJ's Amateur Contact Log. Ideally both of these clients will be cross platform, working on Linux, FreeBSD, OSX, and Windows. Finally I think having a web interface that interacts with the API would be great as well.

I will be working on this project as part of #100DaysOfCode officially starting on September 18, 2023.

Dependencies Installation

$ poetry install

Running QSLlink for development

$ uvicorn qsolink.qsolink:app --reload

Future Integrations

I think integrating with a callsign lookup database like HamDB.org or callbook.info would be fantastic. I should also ensure that QSOLink can post our logbook to the QRZ Logbook which has an API as well.