现在看到一个 self-hosted 的开源项目第一反应就是找 docker/docker-compose 部署方式，包括自己哪怕只是写一些小服务也是会先强迫症似的把 Dockerfile 和相应的 docker build + docker push GitHub Actions 写完，一直觉得是一个标准的 SOP，但最近想要部署 goatcounter 这个项目的时候发现作者对于容器化带来的复杂度和维护成本一些讨论很有意思 #TIL I'm not a huge fan of Docker, and to be honest don't feel like installing it, maintaining a Dockerfile, dealing with support requests, etc. There are only so many hours in a day, and I don't see how this improves the quality of the product. I also feel it's rather superfluous for a project like this, as it's not a Rails project with loads of dependencies or some such

现在看到一个 self-hosted 的开源项目第一反应就是找 docker/docker-compose 部署方式，包括自己哪怕只是写一些小服务也是会先强迫症似的把 Dockerfile 和相应的 docker build + docker push GitHub Actions 写完，一直觉得是一个标准的 SOP，但最近想要部署 goatcounter 这个项目的时候发现作者对于容器化带来的复杂度和维护成本一些讨论很有意思 #TIL

I'm not a huge fan of Docker, and to be honest don't feel like installing it, maintaining a Dockerfile, dealing with support requests, etc. There are only so many hours in a day, and I don't see how this improves the quality of the product. I also feel it's rather superfluous for a project like this, as it's not a Rails project with loads of dependencies or some such

https://github.com/arp242/goatcounter/issues/34

GitHub

Docker · Issue #34 · arp242/goatcounter

I would love to make a pull request but I'm really not quiet strong with the Dockerness. I think having a Dockerfile, docker-compose.yml, and an official docker image might make it easier for c...