Summary of changes
This release makes some fairly big changes to how the script is configured and adds a new "monitoring" feature (courtesy of @benjmarshall) that allows the script to run in the background and monitor a folder for new FIT files and upload as they appear (previously, this could only be done if you ran the script on some sort of interval using an external scheduling tool like cron or Windows Task Scheduler).
In general, the README explains how to use these new features. Some highlights:
- Rather than being configured with environment variables (with the
.envfile), a JSON config file is used instead (.config.json). This can be manually created, or will be automatically created if the script is run with the-sflag (it will also be created if any of the needed values are missing). - Part of the config is a
fitfiles_pathoption, which specifies a default directory to use when monitoring or uploading files. The script will attempt to auto-detect your TPVirtual data folder, but it can also be entered manually - The monitor function
-mallows for the script to auto-detect when new FIT files are created (such as at the end of a workout). On the PC for my trainer, I have this configured to run automatically when logging into Windows, and leave the script running in the background so it will auto-process/upload the FIT file created at the end of my ride.- More specifically, I created a task to run at user logon that runs the program
cmdwith arguments/C C:\Users\username\fit_file_uploader\.venv\Scripts\activate.bat & python garmin.py -min the folderC:\Users\optiplex3060-1\fit_file_uploader, which appears to be working fine
- More specifically, I created a task to run at user logon that runs the program
What's Changed
- Improvements from @benjmarshall by @jat255 in #13
Full Changelog: v1.0.0...v1.1.0