ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
To exec into a container in a pod, I use the following two commands (note the template flag in the first command trims the output to print just the name of the pods): $ kubectl get pods --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}' app-api-6421cdf4fd-x9tbk app-worker-432f86f54-fknxw app-frontend-87dd65d49c-6b4mn app-rabbit-413632c874-s2ptw $
The documentation says that the TargetRefName can be updated when "PR retargeting feature is enabled" but I can't find this option anywhere and can't see any documentation about how to enable it either. How do I enable PR retargeting so that I can update the PR's target? https://learn.microsoft.com/en-us/rest/api/azure/devops/git/pull%20requests/update?view=
In my internal work network, whenever I launch dig against a particular hostname, I get result similar to this: ;; ANSWER SECTION: some.internal.host.com. 10 IN A 10.210.54.121 If I keep spamming the same dig some.internal.host.com command, the response always has a single A record, but the IP address is changing between calls. I assume it is some form of lo
I always thought that the default gateways has to be on the same network as the server/client trying to connect to the internet. However today I rented a server from Hetzner and the server is able to connect to the internet even though, as it seems to me, the default gateway is definitely not connected to the same network. Also the netmask seems to be set to
I was wondering how I can set the system path variables in the GitHub actions workflow. export "$PATH:$ANYTHING/SOMETHING:$AA/BB/bin"
I am trying to configure wireguard to work as a VPN server. The main problem is, that the gateway only forwards the VPN server ip to other server, not my client IP. My setup is the following: - server A (10.10.0.4) / CLIENT (10.10.1.3) -> wireguard server (10.10.1.2) -- (10.10.0.2) \ - server B (10.10.0.3) The wireguard server runs on a machine with two i
Diagnosing intermittent connection pool exhaustion in node-postgres (pg) is complicated by the fact that multiple root causes produce the same 'timeout exceeded when trying to connect' error. A leaked client (missing release) and an event-loop stall that delays release callbacks can both leave the pool empty, as can a pool size that is too small for burst co
Goal Establish a reproducible development environment where language servers launch automatically when a buffer is opened. Unresolved Constraint The current auto‑start mechanism in nvim‑lspconfig triggers for any buffer matching a filetype, but the documentation does not specify limits such as file size, complexity, or user‑defined predicates. This omission
The story so far: I have installed Postgres on my Linux based desktop (HOST). I have created a test database, with test data, on HOST. I have added to the end of the pg_hba.conf file on HOST: host samerole all 0.0.0.0/0 md5 I have added to the end of the postgresql.conf file on HOST: listen_addresses = '*' I have installed PGAdmin4 on the Linux virtual machi
kubernetes
azure
docker
nodejs
neovim
linux