3 ms·
OP here, thanks! It is fun to learn, but it sucks to yak-shave [1] all the time. The simplicity of the stack lets me walk away for days (or years) at a time,
by simplecto 6y ago
OP here, thanks!
It is fun to learn, but it sucks to yak-shave [1] all the time.
The simplicity of the stack lets me walk away for days (or years) at a time, come back, and easily ship changes. No need to remember esoteric commands, configs, or get bitten by strange infrastructure upgrades.
I'm lazy, and I'm just looking for ways to be lazier. :-)
- wiredfool 6y agoDid you mean to expose your postgres port to the world? Adding the port declaration to the docker file exposes it to other containers on the same network/machine, adding it in docker-compose exposes it to the world.
- simplecto 6y agoThat is explicit. Now that I think about it, I should update the article with how I do it now. I explicitly bind the external port only to the ZeroTier interface. In fact, my configs have changed a bit: instead of: ports: - 5432:5432 I now use the IP of the zerotier interface: ports: - 192.168.111.123:5432:5432 Now the only way to reach that port is via the vpn.