Rogue site control and php-fpm modification

Sorry, completely missed your posts. I'll look through the code the next few days.

 

The ISPConfig updater has an option to run a php file for a specific database update. You can find these files in install/patches/ folder. The name must match the sql incremental file. Currently, the name would have be upd_0085.php so that it gets run when with the 0085 sql file (when we create it by moving the code from dev collection to a file with that name. see the existing two files for the file structure, basically it just contains a function that is called before the sql insert and one that is called after insert.

I would say that we should add the path as an option somewhere under System > server config (web ?). The paths from the distribution specific conf array are written in installer_base.lib.php and update.lib.php. see installer_base.lib.php around line 300+

One thing that we should consider is to add an option under System > server config to hide the php_fpm_isolated_process option in the website settings completely as not all systems have systemd installed and this options won't work without systemd. That way we can hide it on older systems. But that's something that I can add myself later as well so you don't have to find out how to implement that in the interface

 

That would be great!

That's my guess as well. Most likely it's just a difference in the paths.

 

If it's well written and tested on Debian Ubuntu and RHEL derivates and the author assures that he will maintain it for the next years, then I might integrate it into the core. I'm currently working on php-fpm inside Docker containers for isolation, which would make such a cgroup-based solution likely superfluous.

 

You can already have several ISPConfig systems offer the same sites, this feature is called server mirroring. You can find an example configuration for that in the multiserver guides.

 

There is no dependency on Glusterfs for that setup; it was just one possible example we chose at that time. You can use any network storage for /var/www that allows you to mount the storage on two servers, from various OS software (e.g. Ceph or another kind of highly available NFS server) to cloud services or commercial storage appliances. For installation, one would use the auto-installer today for the ISPConfig part. Mounting your network storage to /var/www must be done by you though, depending on the storage type you use.

Btw: Even if we use Docker more deeply in ISPConfig, there would be no benefit or difference in using Docker here as Docker would require a shared storage for the volume that holds the websites in the exact same way.