It has taken a while, but v5.0.0 is finally here. This is the biggest release since the project began as Statistics for Strava.
A few months ago, Strava announced changes to their API program that affected a lot of developers.
In hindsight I’m really happy that Strava did what they did, Dreeve is now 100% self-hosted and no longer depends on Strava.
For anyone who never heard about Dreeve (or Statistics for Strava):
Dreeve is a self-hosted, open-source dashboard for your sports and fitness data

The biggest changes that v5.0.0 includes:
- Full rebrand, moving away from Strava branding
- Uploading raw FIT, TCX and GPX files (importing your activities from Strava is still fully supported)
- A proper admin panel, moving away from YAML based config files
If you are upgrading from v4, be sure to check the migration guide: https://docs.dreeve.app/#/getting-started/migrating-from-v4
As always, thanks for your feedback and I’m looking forward to more feature requests! Stay fit, stay healthy 💪
- Example: https://demo.dreeve.app/dashboard
- GitHub: https://github.com/dreeveapp/dreeve
- Docs: https://docs.dreeve.app/#/


lol, so it came to the point when developers need to explain what tools are they using 😆 I don’t care how it’s done as long as it works as intended
Didn’t downvote you but, even as someone who dabbles in AI, and who does not outright reject AI assisted opensource projects, I do really care about the content, the inner workings of said app. If for nothing other than I don’t want to mop up an attack because I deployed something unsafe on my network. So, while I am quite open to AI assisted projects, prudence is the operative word.
Well, some people care about security and want to stay away rom fully vibe-coded apps. So I get that these kinds of posts benefit from a disclosure