It would seem I ran over you a little on this one. I didn’t initially pick up on topic/Linting/ImageUpdate01 was updating to the latest version of php and also moving to Trixie. You could likely merge feature/php-apache-update into your this branch and then when we’re ready open a PR to merge everything into main.

 

I was able to use a variety of linting tools to migrate the code base from 8.2 to 8.5. I think it’s likely in fairly good shape and the site seems to function without issue but someone who knows php well should take a look at it.

 

Thanks,

 

Steve Gilmore

 

From: Chris Bier <chris.bier@cymor.com>
Sent: Wednesday, February 25, 2026 8:23 PM
To: KCLUG <kclug@kclug.org>
Subject: Re: Site requirements and Move

 

I have a PR I'm working on to bump it up to version "8-apache". The container isn't in production. On Wed, Feb 25, 2026, at 08: 58, Gilmore, Steve wrote: Johnathan, Thanks for the reply. I appreciate where you’re coming from on keeping prod as

I have a PR I'm working on to bump it up to version "8-apache". The container isn't in production.

 

On Wed, Feb 25, 2026, at 08:58, Gilmore, Steve wrote:

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-89ad17cca246e8a6ce742b5b89ce65b34ce6223204a282e45f72b4f758ff6401

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.

_______________________________________________

KCLUG mailing list -- kclug@kclug.org

To unsubscribe send an email to kclug-leave@kclug.org

https://kclug.org/mailman3/postorius/lists/kclug.kclug.org/

 

 



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.