PHP sessions are global variables that transmit data stored during web visits across multiple pages, i.e., they are not lost when moving from one page to another. PHP accomplishes this by assigning unique IDs to visits (sessions) and creating files in the server-side file structure associated with those IDs in which it stores the data required for the session. The system places these files in a specific directory, usually tmp, which is normally deleted by the garbage collector after a specified time. However, the situation is sometimes not so obvious. This is because if the PHP environment on the server changes, the garbage collector may not be able to delete these obsolete, unnecessary session files. In this description, we will look at how we can use our own solution to ensure that these session files are deleted when the default cleaning system cannot remove them.

There have been several base system updates for Drupal 9 CMS in recent weeks, so it's worth reviewing its update mechanism as before for the Drupal 8 update. In this description, I'm going to update the Drupal 10 website installed on the Debian 9 (Buster) perfect server from 9.1.2 to 9.1.4, so here we now jump to several versions at once. There are two ways to do this: first with a composer, and then look at the manual update.

When updating our packages, the APT package manager may hold some pieces. This is mostly because a particular program sometimes goes through changes that change the package dependency of the base software. In this case, you would need additional new packages, sometimes ones that require the replacement of other packages. Thus, in some cases, the normal-mode package update does not perform an update to such software, but APT leaves the matter to the user. In this brief description, let’s look at an example of how to update our packages withheld in this way.

On December 2019, 4, Drupal released its currently latest base system, 8.8.0. We’ve talked about how to easily upgrade the Drupal base system before, but more has changed in this release, so we need to get a little deeper into things. So in this description we will look at how to upgrade our Drupal base system from 8.7.10 to 8.8.0.

When running websites, the size of the databases may reach our free space on the partition, or we may want to migrate our databases to an SSD drive, for example, for performance optimization purposes. Whatever the reason for this, we can learn from this description how to migrate binaries containing databases to another partition or drive.

Learn how to easily upgrade your Drupal 8 base system with Composer