Repository navigation
Replies: 1 comment
|
Thank you @tam481 for the request. Running the server in a container is feasible: it is one static Go binary with the SPA embedded, all of its state lives under its data directory, and the health check is already at /api/health, so a Dockerfile and a compose example would be small. What I cannot do is maintain that image. I run NetPulse as a plain Go binary behind GoDoxy and I never deploy it with Docker, so I would be publishing an image I do not use and cannot validate against real deployments. There seems to be demand for one, though, and I would be glad if a contributor took it on. If someone wants to own it, I will help with the packaging details (a volume for the data directory, environment variables, health check), with an image build and publish workflow in this repository, and with a link from the README. Say so here if you are up for it. |
Uh oh!
There was an error while loading. Please reload this page.
Hello
Hoping you'd consider making a container image for netpulse with support for docker compose and reverse proxies such as Traefik.
Thank you in advance
All reactions