https://github.com/scriptraccoon/run-diary

Clone of Strava's training log
https://github.com/scriptraccoon/run-diary

Last synced: 6 months ago
JSON representation

Clone of Strava's training log

• Host: GitHub
• URL: https://github.com/scriptraccoon/run-diary
• Owner: ScriptRaccoon
• License: mit
• Created: 2022-08-04T20:44:09.000Z (almost 4 years ago)
• Default Branch: main
• Last Pushed: 2024-01-26T00:06:21.000Z (over 2 years ago)
• Last Synced: 2024-05-30T16:49:59.463Z (about 2 years ago)
• Language: Svelte
• Homepage:
• Size: 71.3 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Run diary

In the paid version of [Strava](https://www.strava.com) the training log is a very useful feature. Unfortunately, it's not available in the free version. But you can just build it yourself! You can use this repository as a template for that.

![Screenshot](screenshot1.jpg)

The diary lists all your runs in form of "bubbles" whose sizes correspond to the total amount of kilometers on that day. By clicking on them you get a more detailed overview over the runs. They are linked to the respective Strava pages with more details.

 

![Screenshot](screenshot2.jpg)

Of course you have to import your runs from Strava (see below).

## Usage

1. This is a [Svelte](https://svelte.dev) project. When you clone it, run `npm install` to install all the packages. Run `npm run dev` to start the development server and `npm run build` to build the app for production.

2. In the folder `public/data` there is a `export.csv` file which should contain all your runs. The columns are as specified there. I use [flink](app.flink.run) to export my runs from Strava. (I have to do this manually on a regular basis to keep the runs uptodate, you can probably automate this. The best alternative would be to use the Strava API, which however requires more effort.)

3. Change titles and texts in the components as you like.

4. Deploy the site wherever you want. (In my version, I have deployed it to Netlify and password-protected it via a serverless function, since I want to keep my runs private. So this here is actually a simplified version of what I actually use for myself.)

5. The responsive design makes it possible to use the site on a phone as well. I put my run diary on the phone's start screen.