Re:Show HN: Workout Tracker – self-hosted, single binary web...
by easyas124 on Thursday February 29, 2024 @07:54PM
(#39557221)
Why would you use Docker at all? Just run the application behind a reverse proxy. Docker doesn't get you anything except an extra management headache and an abstraction that happily punches holes in your firewall.
Re:Show HN: Workout Tracker – self-hosted, single binary web...
by alex_lav on Thursday February 29, 2024 @08:29PM
(#39557446)
I mean...the entire reason docker exists? So that I don't have to understand and manage everyone else's (sometimes insane) build and deploy processes?
Re:Show HN: Workout Tracker – self-hosted, single binary web...
by ClumsyPilot on Thursday February 29, 2024 @08:53PM
(#39557608)
App A requires a version 2 of whatever which conflicts with version 3 of whatever required by app B, and uses same port as app C and doesn’t like the smell of app D. Meanwhile app Z has to be compiled from source with a specific version of python and only installs on Tuesdays, buts it’s Wednesday if mercury is retrograde
Re:Show HN: Workout Tracker – self-hosted, single binary web...
by QuinnyPig on Thursday February 29, 2024 @08:59PM
(#39557656)
It may help to view it primarily as a packaging system.
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.