dave bonner @rascalking@octodon.social

@mallaidh well, it's only been around for...*googles*...at least 21 years.

@nivex and we appreciate it.

happily, this seems to have been something wrong with the socat processes running inside the containers. changed one of them to an nginx container, and everything Just Worked. kinda annoyed, but not enough to really spend any time root causing this. going to just take the win.

trying to figure out how to tell a docker container from compose A to communicate with a container from compose B. set up a simplified set of compose files with containers running socat to try and figure things out.

now, of course, i can't even talk to a single container in one of those composes from the host. and am wondering if anything will ever work ever.

@staticsafe which is, of course, a long-winded way to squee that somebody is getting to read one of my very favorite books for the first time.

@staticsafe those are both excellent books. you are in for tons of fun.

let us know what you think of neuromancer... I'm curious to see how it lands on someone who's seen/read all the stuff it's influenced but never read it.

@tcql @staticsafe @MightyPork maybe also determined by whether you've toggled the "don't show sensitive information on the lockscreen" button?

i'd been trying to stick to my current side project (android app to keep track of whose turn it is on things my kids fight about, as an excuse to learn some #kotlin), but i've given up at the "now plug in an orm for persistence" stage for now.

time to start playing with #rustlang.

@wim_v12e thanks!

@skroo sorry, link helps: https://stackoverflow.com/questions/42149529/how-to-reload-environment-variables-in-docker-compose-container-with-minimum-dow

@skroo this SO post suggests all you need to do is "docker-compose up" again (with an optional "-d" if you're running it detached), and it will take care of recreating and restarting any containers that consume that env file.

@skroo i'm guessing, but it sounds like you're talking about an env_file being referenced from a docker-compose.yml (ie. https://docs.docker.com/compose/compose-file/#env_file)? if so, you wouldn't need to rebuild the images, just restart the application.

what i can't manage to find, though, is whether docker compose restart will pick those changes up, or if you have to do a down and then an up.

@InspectorCaracal ah, bummer. thanks for answering!

am i just missing something, or is there no way to have two "home" columns #onhere? some folks i follow tend to boost a lot, and it drowns out most everyone else in that column. looking to set up "home with boosts" and "home without boosts" columns, but can't figure it out.

why why why why WHY does python's argparse.error exit with a status code of 2? WHY?!

my sense of unix aesthetics is going to force me to basically reimplement that method just to get the correct exit code.