February 2026 - KCLUG

Re: Site requirements and Move
by Gilmore, Steve 07 Mar '26

07 Mar '26

Johnathan, Thanks for the reply. I appreciate where you're coming from on keeping prod as simple and stable as possible, I wasn't trying to kick off a debate. I asked because I genuinely wanted to understand your perspective. I'm with you on "no compilers on exposed prod boxes." Where containers have worked well for us is leaning on them in the build pipeline, then keeping the production image as minimal as we can: just the app (often just a binary) and whatever it needs to execute. Sometimes that's even FROM scratch, or something tiny like Alpine, rather than starting from a full Ubuntu base and carrying around things we don't need. That said, you're right that containers are another layer to operate, and it's worth treating that as real complexity. In this case, it looks like Chris already has a working example in the repo I cloned it yesterday to build one myself and found it there. One thing that stood out is the base image/deps. For reference: https://hub.docker.com/layers/library/php/8.2-apache/images/sha256-89ad17cc… It looks like some dependencies are outdated/vulnerable, so my inclination is to bump to the latest viable base and see what breaks, then work forward from there. Thanks, Steve Gilmore ________________________________ CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be Garmin confidential and/or Garmin legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.

4 5

Site requirements and Move
by Chris Bier 24 Feb '26

24 Feb '26

Hi All, Here are my thoughts on a site move: We don't have to keep the Website and Mailing list on the same server, but here are the requirements: - 21GB of storage for everything including the OS - 1 CPU or better - 2GB RAM or better We're looking into containerizing the site and building it with a Static Site Generator, which would make hosting it easier. The mail server needs to have: - A good Reverse DNS - A non-residential IP with a good reputation (to help keep it off black lists) - Postfix (preferred) - Mailman3 - Optional: IPv6 would be cool For any of these, I think we'd want at least 3 people with access. So far, I've heard 2 offers to host us. (Please reply with what you could provide) I don't see why we couldn't have multiple people host the website. Our DNS provider (NameCheap) doesn't seem to support Round-Robin DNS, but I'm sure we could come up with something. I think the Mailing list would have to be in just once place. We could have a rsynced backup, though. What does everyone think?

3 4

KCLUG Feb recap + website move status + Next meetup Thu Mar 19 (Leawood Pioneer, 6–8pm)
by Gilmore, Steve 24 Feb '26

24 Feb '26

Hi everyone, Thanks again for the great discussion last meeting. Sorry for the delayed follow up. Here’s a recap plus where we are on the website move, and details for our next meetup. Next Meetup (3rd Thursday - same location, room already reserved) Date: Thursday, March 19, 2026 Time: 6:00pm – 8:00pm Location: Johnson County Library – Leawood Pioneer 4700 Town Center Dr, Leawood, KS 66211 Room: Leawood Conference Room Feb meeting recap (highlights) Website / hosting Our hosting provider Netstandard is getting out of virtual hosting, so we need to move the KCLUG website. Volunteers so far: * Billy Croan offered to host (VM with public IP) * Brent may be able to host as well (checking on public IP/VM) * Chris Bier is current site contact/maintainer * Hal Duston maintained the site back in the 90s Current site repo: https://codeberg.org/KCLUG/website (Chris made it public) Stack / requirements (current + near-term): * Apache + PHP (currently PHP 8.2.29) * We want updates to be doable by multiple people (reduce single points of failure) * Directionally: we’d like to keep “site vs. mail” separable, and it would be nice to keep components in separate containers where it makes sense, but no final architecture decisions yet. What matters most day-to-day: keeping the front page fresh. Mailing list / mail server (related but can be separate) From Chris’s follow-up, the mail host needs good deliverability: * good reverse DNS * non-residential IP with a decent reputation * Postfix (preferred) * Mailman3 * optional IPv6 (Website and mail do not have to live on the same server.) Domain / “single point of failure” Vaughan shared a cautionary tale from another LUG losing their domain due to renewal/ownership process breakdown. Good reminder to ensure we’re not relying on a single person/account for critical access. Current note: Billy has access to the domain/registrar. (Thank you!) Vaughan also suggested a practical “corporate-style” mitigation to avoid single points of failure: * keep registrar credentials in a shared password vault * set registrar contact email to a small group/distribution list * ensure at least 2–3 active admins always have access Quick replies requested (so we can move forward) Please reply to the list with any of the following: 1. Hosting offers (website and/or mail): * VM or bare metal? Public IP? Can you support reverse DNS (mail)? * Rough specs are fine (CPU/RAM/storage) 2. Access / admins: We should have at least 3 people with access for: * domain/DNS * website host * mail host * If you’re willing to be an admin for any of those, please say so. 3. Codeberg contributors: * If you want access to the Codeberg org/repo to help maintain the site (or explore a static site generator approach), reply and Chris can add you: https://codeberg.org/KCLUG What folks are doing with Linux (round-robin from the room) We had a lot of shared interests: gaming, low-level programming, not using Windows!, tinkering/hacking, embedded, networking, and a ton of self-hosting (Plex/Nextcloud/backups/media servers). Also: lots of interest in Kubernetes and containerization. My proposed March topics: * Steve (myself) will present: “Linux Containerization” (practical overview + discussion). * Chris: if you’d like to add a short Kubernetes segment or demo, that’d fit great, totally optional. If anyone else would like to present or share something, please let us all know! See you all on Thursday, March 19 (6–8pm) at Leawood Pioneer in the Leawood Conference Room. Thanks, Steve Gilmore ________________________________ CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be Garmin confidential and/or Garmin legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.

1 0

Re: List on Black List
by Chris Bier 21 Feb '26

21 Feb '26

MXtoolbox says we're off all the lists now. Let me know if anyone is still having issues. On Fri, Feb 20, 2026, at 21:51, Chris Bier wrote: > Should be good now. > > On Fri, Feb 20, 2026, at 13:20, Jonathan Hutchins wrote: >> >>> On 02/20/2026 1:05 PM CST Chris Bier <cymorc(a)gmail.com> wrote: >>> >>> Looks like we've recently been put on a black list. I've requested we be removed, but Comcast seems to be blocking us right now. >>> >>> Chris >> Perhaps something to do with the 10,000 probing hits per day maybe? >> -- >> Jonathan

2 1

Website Repo
by Chris Bier 21 Feb '26

21 Feb '26

Hi All, We have an Org and Repo for the current version of the website on codeberg.org that will update the site automatically. If anyone is interested in joining the Org there or building an alternate version of the site (Static Site Generators or other), let me know and I can add you. https://codeberg.org/KCLUG Chris

1 0

List on Black List
by Chris Bier 20 Feb '26

20 Feb '26

Hi All, Looks like we've recently been put on a black list. I've requested we be removed, but Comcast seems to be blocking us right now. Chris

2 1

Hello + domain advice
by vaughan.schmidt＠gmail.com 20 Feb '26

20 Feb '26

Hi, new KCLUG list member here. I signed up after the KCLUG got a shout out on Garmin's Linux Users Slack channel earlier in the week. Anyways: I saw the recent discussion on hosting, and a couple of the comments about single points of failure / 1 contact person made me think to chime in here: Make sure you folks have a good handle on who owns the domain itself, and ideally find a way to mitigate single point of failure there. I've been a member of UCLUG (Upstate Carolina LUG, Greenville SC) for probably 20 years, but have been remote since I moved out of state ~11 years ago. Looks like UCLUG domain name itself just got poached and lost when it was not promptly renewed. I haven't kept up with the very latest, but a lot of the original old guard in that UCLUG have become less active as they've entered retirement, shifted focus, whatever. Aomewhere along the line, the ball got dropped. I did check whois for kclug, and it looks like it is right in the middle of a renewal. Registrant is hidden, but hopefully its one of you. Cheers, and hope to make it to a meeting at some point, -Vaughan

3 2

RE: Hello + domain advice
by Chris Bier 20 Feb '26

20 Feb '26

Welcome, Vaughan! Thanks for the reminder! We've currently got 3 people that have access to the DNS provider and renew when it comes up. Yeah, once it's gone, it's rare to get it back. We've actually got kclug.org, kclug.com, and kclug.net, but haven't really used the .net and .com. Chris On Fri, Feb 20, 2026, at 08:53, vaughan.schmidt(a)gmail.com wrote: Hi, new KCLUG list member here. I signed up after the KCLUG got a shout out on Garmin's Linux Users Slack channel earlier in the week. Anyways: I saw the recent discussion on hosting, and a couple of the comments about single points of failure / 1 contact person made me think to chime in here: Make sure you folks have a good handle on who owns the domain itself, and ideally find a way to mitigate single point of failure there. I've been a member of UCLUG (Upstate Carolina LUG, Greenville SC) for probably 20 years, but have been remote since I moved out of state ~11 years ago. Looks like UCLUG domain name itself just got poached and lost when it was not promptly renewed. I haven't kept up with the very latest, but a lot of the original old guard in that UCLUG have become less active as they've entered retirement, shifted focus, whatever. Aomewhere along the line, the ball got dropped. I did check whois for kclug, and it looks like it is right in the middle of a renewal. Registrant is hidden, but hopefully its one of you. Cheers, and hope to make it to a meeting at some point, -Vaughan *___**___**___**___**___**___**___**___**___**___**___**___**___**___**___*__ KCLUG mailing list -- kclug(a)kclug.org To unsubscribe send an email to kclug-leave(a)kclug.org https://kclug.org/mailman3/postorius/lists/kclug.kclug.org/

1 0

what to do with a liftgrid mining rig?
by David Nicol 18 Feb '26

18 Feb '26

Liftgrid appears to have gone defunct. I've got one of their HNT mining apparatusses installed in my attic, still running as far as I know. Would any of the LoRa enthusiasts here like to take it over? I'm not entirely sure what "take it over" means. -- "Plot complication appearing on sensors now"

3 4

KCLUG hosting
by Jonathan Hutchins 18 Feb '26

18 Feb '26

We have several offers to host the static pages. That's not hard, any of us with a broadband connection could do it. That does leave us with a single point of failure if we lose the person providing it. The same goes with the system being as close to a box-stock Debian server - if the maintainer vanishes that's a lot easier for a new person to understand and recover. We do need the ability to send email via smtp, and that needs to come from a commercial, not residential address. There may also be an issue with the volume of malicious connection attempts, I don't know if that would be significant to a provider. It would also be nice to have a local provider, just to promote the concept of a Kansas City site/service. With that setup we could easily host a podcast with archives as well. -- Jonathan

6 11