It had started as http → https, but then the company at the other end of the line have removed their v1 databases all together; then current openvpn-monitor undergoing dockerization was not compatible with v2; then an act of configuring this new (1.0.0) version required further modification of Dockerfile.
Now the only way to pass the configuration is upon build, which is not ideal. Those docker run -e envs would be welcome - see below ↓
Todo:
– fix confd templates for openvpn-monitor 1.0.0 to parse them properly. More detail: 20009549a2109f2fad13f8bfabefd8790539bc15
– and also.. I can't remember.. idk. I'll be porting it to armhf now btw
It had started as
http
→https
, but then the company at the other end of the line have removed their v1 databases all together; then currentopenvpn-monitor
undergoing dockerization was not compatible with v2; then an act of configuring this new (1.0.0) version required further modification ofDockerfile
. Now the only way to pass the configuration is uponbuild
, which is not ideal. Thosedocker run -e
envs would be welcome - see below ↓Todo: – fix
confd
templates foropenvpn-monitor 1.0.0
to parse them properly. More detail: 20009549a2109f2fad13f8bfabefd8790539bc15 – and also.. I can't remember.. idk. I'll be porting it toarmhf
now btw