0
5
superpants

@lemmy.world

superpants 14 points 4 days ago

Why you gotta call me out like this?

path: 0 26230600 26232546, hotness: undefined, score: 14, children: 0
superpants 5 points 3 years ago

A plug for the pro Kubernetes crowd:

I run microk8s on a 3 node cluster, using FluxCD to deploy and manage my services. I also work with Kubernetes at work, so I'm very familiar with the concepts. But I will never use anything else.

If you want maximum control and flexibility, learn Kubernetes. For a lot of people (myself included) it's overkill, but IMO it's the best.

My main gripe with docker-compose, which is what I used to use, is that service changes require access to the machine. I have to run commands on the host to alter services. With Kubernetes, and more precisely a GitOps model, you can just make a commit to a git repo and it will roll out.

path: 0 6540700, hotness: undefined, score: 5, children: 3
superpants 2 points 3 years ago

Sorry, I misread your compose file. It should be the name of the PG container, so db:5432

path: 0 1807505 1812853 1819783, hotness: undefined, score: 2, children: 1
superpants 2 points 2 years ago path: 0 11401218, hotness: undefined, score: 2, children: 0
superpants 1 point 3 years ago

The python container should connect on postgres:5432 not localhost. To the web container, localhost is itself, not the physical host running docker

path: 0 1807505, hotness: undefined, score: 1, children: 3
superpants 1 point 3 years ago
path: 0 1819749, hotness: undefined, score: 1, children: 0

thanks for using Leebra!

go to feed...