Fully retired now and one of the things I’d like to do is get back into hobby programming through the exploration of new and new-to-me programming languages. Who knows, I might even write something useful someday!

  • 5 Posts
Joined 1 year ago
Cake day: July 4th, 2023

  • They are just the biggest asshole in the room.

    So one day the different body parts were arguing over who should be in charge.

    The eyes said they should be in charge, because they were the primary source of information about the world.

    The stomach said it should be in charge because digestion was the source of energy.

    The brain said it should be in charge because it was in charge of information processing and decision-making.

    The rectum said nothing, just closed up shop.

    Before long, the vision was blurry, the stomach was queasy, and the brain was foggy.

    Assholes have been in charge ever since.

  • That’s what I worked through this morning. I learned elsewhere in these comments that users have both names and IDs and that docker references IDs.

    I’ve changed ownership of the files and folders a few times. First to match the default setting in docker-compose.yaml, then as I tried different user IDs. Always the same message.

    I did additional research and found references to something known as “mounting volumes”, but have not yet had a chance to explore that angle further. It’s not mentioned in the GTS documentation that I can see, so I just assumed (I know…) that the .yaml file was taking care of it.

    At this point, I suspect that there is something else going on, possibly with ports. I had to do a bit of fiddling with ports to kill a bind error resulting from the fact that there is another service hooked up to ports 80 and 443. I’m only guessing, but maybe it’s unable to create the database because it needs to do so via those ports. That doesn’t sound quite right to me, but it’s not like I have any real clue!

    One thing I noticed is that docker-compose is recommended by GTS, so I installed it and that really blew up in my face, so I went back to docker compose as I’ve used elsewhere.

    Research continues…

  • Why not? The last decade before semi-retirement I had all the different ways to get in touch with me restricted to my phone. My work computer had no email client, no messengers, nothing. I even helped lead the charge to eliminate desk phones.

    That little display may have been the single greatest priductivity booster ever. It stayed on a shelf across the room on do not disturb. The only people allowed past the DnD were my wife and my son. If there really was a work emergency, a manager or coworker knew where to find me to tap me on the shoulder.

  • The Stalwart mail server allows for that. They call them “spam traps”.

    Basically, it’s a real email address that literally never gets used or referenced anywhere, thus assuring any email received is unsolicited by definition. Stalwart’s spam engine uses any such email to help train the spam filter.

    I can’t imagine that Stalwart is only one implementing such a system.

    I’ve never used Stalwart, but it’s the email server I’ve selected should I decide to do what everyone tells me I shouldn’t: run my own server for me, my wife, and the two domains we control. Their documentation is basically a master class in email.