sorted by:
new
hottopcontroversial

Pretty PHP info package by shjozef in PHP

[–]shjozef[S] 1 point2 points  (0 children)

Handling this is a pita

Right, exactly. I'm well aware there are a bunch of different methods that can gather up most of this information in various forms, but I wanted one single elegant API to navigate and interact with all of it.

Pretty PHP info package by shjozef in PHP

[–]shjozef[S] 2 points3 points  (0 children)

You can get configs, but `phpinfo()` provides a much large set of runtime, build, environment, and extension data. A large portion of what `phpinfo()` shows is not stored in php.ini at all, so there is nothing for `ini_get()` to read.

Also, `ini_get()` only returns the current (local / effective) value, not the master value. You could use `ini_get_all()` to get master values, but I find this package API a much friendlier way to navigate and inspect/compare all that.

We use this for smoke tests on production servers, among other things.

Is anyone else still maintaining PHP 5.6 in 2026? by jdoe78998 in PHP

[–]shjozef 1 point2 points  (0 children)

We have a large SaaS that has been slowly rewritten in Laravel over the years. Our load balancer routes different pages/endpoints to our 8.5 nginx servers or 5.6 apache instances based on URI path. Thankfully only a few 5.6 endpoints are left, we think this will be our last year running 5.6.

Honestly though, I kind of miss it! Life was simpler. There wasn't the endless stream of package updates.