Show HN: Workout Tracker – self-hosted, single binary web application
github.com
Show HN: Workout Tracker – self-hosted, single binary web application
1–10 of 102 posts
Re: Show HN: Workout Tracker – self-hosted, single binary web application
#2Re: Show HN: Workout Tracker – self-hosted, single binary web application
#3Re: Show HN: Workout Tracker – self-hosted, single binary web application
#4nice. How do you track teh distance (walked or running?)
[1] https://github.com/tkrajina/gpxgo
[2] https://github.com/tkrajina/gpxgo/blob/5e7c336e94dac3583a07c...
Re: Show HN: Workout Tracker – self-hosted, single binary web application
#5Clean UI, too. Interested to hear your thoughts on HTMX when you get around to eval-ing it
Re: Show HN: Workout Tracker – self-hosted, single binary web application
#6Re: Show HN: Workout Tracker – self-hosted, single binary web application
#7Re: Show HN: Workout Tracker – self-hosted, single binary web application
#8I love the minor movement toward self-hosted web apps. I wish they were easy enough to setup as installing an app on Android or iPhone.
Re: Show HN: Workout Tracker – self-hosted, single binary web application
#9It might be an interesting experiment to have the UI be installable as PWA and thereby not need the electron stack to achieve the common functionality offered by these apps.
Re: Show HN: Workout Tracker – self-hosted, single binary web application
#10I love the minor movement toward self-hosted web apps. I wish they were easy enough to setup as installing an app on Android or iPhone.
Use your old PC, a Raspberry Pi, an EC2 instance, whatever you like, a single small Docker Compose file with Watchtower for auto-updating the container image when new one published etc. I've got self-hosted services that have ran untouched for years this way at home from a handful of lines of YML. Docker Compose will also take care of restarting the service on reboot/powercut if thats a concern.
Given the ubiquity of container images, you can run largely any web application this way and the container image likely already exists - this project also has a Dockerfile and would run fine this way too.