[Feature Request] Accept FitoTrack HTTP POST

[wills106]

FitoTrack has the ability to automatically export a GPX workout at the end of the workout and send it to a server.

Would it be possible to accept these requests?
I have my Workout-Tracker behind a Nginx proxy so I can securely expose Workout-Tracker to the outside world.

I think this would be a cleaner solution than exporting to a folder and then having an additional app running to export it to the server. You wouldn't need something running on the server to except file uploads either.

[jovandeginste]

I never saw that option in fitotrack; thanks for telling me about this! I'm using syncthing for this, but will look into the post! The API is now usable (to fetch statistics), adding a Post route should be easy.

[jovandeginste]

Just noticed fitotrack does not support adding headers; I'm curious if it supports basic auth in the URL...

[wills106]

I don't know if this helps, but it seems to be a relay for accepting FitTrack POST and forwarding the GPX on to Nextcloud?
https://github.com/StratusFearMe21/fittotrack-sync

Edit:
This is the commit on FitoTrack https://codeberg.org/jannis/FitoTrack/commit/d13673068af10352150a4a7d69dafc481b051a93

[jovandeginste]

@wills106 please test and give feedback!

[wills106]

Tried single user so far and it's fine, still need to check a second user to confirm their API key redirects their workout to them and not me for example.

But I have noticed a change in the last 24hrs seems to have decoupled the start and end times for workout.

This was ok yesterday before I updated. But the speed doesn't start with the elevation.

First test of the HTTP upload

Also noticed on "branch master 8175c70" there is a bit of lag moving the mouse up and down on the workouts page.

[wills106]

Also noticed on "branch master 8175c70" there is a bit of lag moving the mouse up and down on the workouts page.

Just on e820e48 now and I'm still getting the Speed / Elevation mismatch.

On the workouts page you can initially move the mouse up and down and it doesn't highlight a row in the yellowish colour. It will then register on one and a few seconds later start to catch-up and highlight other rows.

[jovandeginste]

The mismatch is fixed in #121; I can't seem to reproduce the lag... Could it be related to browser?

[wills106]

Thanks, I'll test the update later today as I don't have a way to update the container at the moment.

[wills106]

Just letting you know the two graphs match up now.
Thanks