Re: Fedora ARM server future use case - Fitness dashboard
Hi Hanku,
Most fitness enthusiasts have favorite apps to track activities and
share with friends. Often, advanced features need a paid membership.
Still, it is limited to fixed features and I get distracted or let
down by certain features, which I don't need. Feature mismatch
persists.
I have 7+ years of fitness data in Strava. The main sport is cycling.
I want to keep the data in my control and design a custom dashboard
using the Fedora server and R Pi. It's not huge data, so I'll stay
away from the cloud. This is proof of concept if I want to expand this
further in the future.
TBH this isn't necessarily a Fedora Server specific thing, it could
also be Fedora IoT or general Fedora.
[Objectives]
Build data pipeline with fitness API (start with Strava).
Set up a database server on R Pi.
Write SQL scripts for data ingest and metrics.
Add Python scripts for calculation and display,
Connect to Dash apps (or equivalent open-source analytics tool).
(Optional) Expand data source to fitness sensors (cycling computer and
Heart rate monitor) for richer metrics.
I would change a lot of the above, like why SQL, a time series DB may
be better for that sort of data.
Will this be of any use or interest to the Fedora community?
I'm sure a general project like this would of wider interest than just
Fedora Server, or even just Fedora.
There's even interest in removing the closed ecosystem such as Strava
for health data entirely so why just limit it to the ability to
visualise data from a proprietary service/stack.
There's PineTime [1] with an open source firmware called IniniTime [2]
with an open GTK3 app to run on Linux [3] so why not go the whole way?
I suggest taking this to the wider fedora devel list.
Peter
[1] https://wiki.pine64.org/index.php/PineTime
[2] https://github.com/InfiniTimeOrg/InfiniTime
[3] https://github.com/alexr4535/siglo