Custom Query (49 matches)
Results (34 - 36 of 49)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#72 | fixed | Create docs infraestructure | borja | borja |
Description |
Using sphinx and rst |
|||
#73 | fixed | Adding manually a workout with decimals on distance breaks the dashboard/profile pages | borja | borja |
Description |
Add a workout manually, in distance set something like 43.2. It will be stored as a float instead of a decimal, causing a big breakage. |
|||
#77 | fixed | Bulk workouts upload | borja | borja |
Description |
So, we already have some code to add workouts in batch mode from a local directory on the filesystem (browser:OpenWorkouts-current/ow/load_workouts.py), but that works only if the workout files (gpx, fit) are located in the filesystem of the computer where openworkouts is running on. In the case of running it in a separate server, users don't have an easy way to upload those workouts. The idea would be to allow users to upload a compressed file containing all the workout files, like a zip, tgz, 7z, etc. Then, openworkouts should uncompress that file into a temporary destination, and run our load_workouts code from there (in a separate, background, process of course). One obvious problem of that is that those compressed files could be quite big, which usually don't work well with traditional http file uploads. One solution for that would be to use something like this js library: |