Today’s DrupalFest post is on the lighter side. I am just going to talk about some of the podcasts I listen to related to Drupal, PHP, and software development in general. I’ll try to cover all the Drupal podcasts I know about. Let me know in the comments if I have missed something. As for others, I am just listing those I listen to.
This is the fourth post in my DrupalFest series and I am excited to keep it going. I want to write about different tools I am aware of for running quality checks on Drupal code. This will be somewhat similar to my last post where I presented various options but focused on the method I use nowadays.
PHP 7.4 introduced the concept of preloading classes (files) on server start-up into the PHP opcache. This gives us performance benefits for sites that tend to load a lot of files with every request; something that Drupal is known to do. A properly configured web server would have opcache (opcode cache) enabled anyway, but preloading brings in a modest performance boost on top of that.
I recently wrote about trying out Ubuntu 16.04 desktop on my other blog. I don’t really use Ubuntu on my laptop but I like to keep up with updates. However, I do use Ubuntu on a couple of my servers and I thought of upgrading on one of them. I was already using PHP 7 for the application there and I figured that would be the easiest one to get started. Well, it didn’t work out but it was a nice learning experience.
Installing PHP from packages is very limited if you want more control over the version of PHP you need. For instance, the php5 package on raring release channel (Ubuntu 13.04) currently has PHP 5.4.9. If you need PHP 5.5 for your project, or (more likely) you need PHP 5.3 or even PHP 5.2 for a legacy project, you can’t use the package. It is best to compile PHP to use the version you need.