←back to thread

827 points surgomat | 2 comments | | HN request time: 0.417s | source

I was the main contributor to workout.lol, an open-source fitness app to easily build a workout routine. The project had traction (1.4k GitHub stars, 95 forks, ~20K visits/month), but was eventually sold due to video licensing hurdles. The new owner stopped maintaining it, and the repo went abandoned.

Over the next 9 months, I sent 15 emails to try to save it : no replies. Feature requests & issues were ignored. The community was left with a "broken" tool let's say.

I couldn't just let it die So I built the new version from scratch with the same open-source spirit, but a better architecture long-term vision, more features and no license problems.

It's called : Workout.cool (https://workout.cool). What it offers: 100% open-source, MIT-licensed - 1200+ exercises (with videos, attributes, translations) - Progress tracking - Multilingual-ready - Self-hostable

I'm not doing this for money. I'm doing it because I believe in open fitness tools, and I’ve been passionate about strength training for 15+ years.

If this resonates with you, feel free to: - Star the repo - Share with fitness/tech friends - Suggest features - Contribute code/design/docs

Together, we can build the open-source fitness platform we all wanted to easily build a workout routine and get in shape

Website: https://workout.cool GitHub: https://github.com/Snouzy/workout-cool

1. nittanymount ◴[] No.44314211[source]
possible to use sqlite for simplicity? really need postgresql ?
replies(1): >>44314472 #
2. surgomat ◴[] No.44314472[source]
not "really" let's say but we chose PostgreSQL mainly for scalability and flexibility long-term.

Features like JSONB, advanced filtering, full-text search, and complex joins are key to how we handle (-exercises specifically- but also user data, and routines in the future)

That said, I totally get the appeal of SQLite for quick local setups. I might add an experimental SQLite mode in the future for simple and/or personal use cases but for now, PostgreSQL is required to support the full feature set

Appreciate the interest (and open to suggestions on making setup smoother) :D

Cheers