Drupal 10, the latest version of the open-source digital experience platform with even more features, is here.Looks like if you have a Debian 10 installed out of the box it uses PHP 7.3, which is awesome.
It took me foreeeeever to realize that the Aegir deb packages refused to install Aegir without defaulting to Apache2 with this configuration. Why? Well it was checking to see if I had PHP 7.2 (only) and if I did then it would allow me to use Nginx.
Can we pleaase pretty please fix this requirement!










Comments
Comment #2
colanWe need a better way to handle this, but given that we're hard-coding
php7.*releases at the moment, the quickest way to handle this is to add entries forphp7.3in Debian's control file. Patches welcome.Having said that, though, anyone know if there's a way to make this more sustainable?
Comment #3
colan@helmo and I were discussing in IRC. It sounds like we can replace all the
php7.x-yentries withphp7-y, which uses the PHP meta packages (which in turn depend on the minor release versions, grabbing whichever version is available).Comment #4
bgm CreditAttribution: bgm commentedTangential, but on the topic of Debian 10: I found that when there are syntax errors in the vhost files (ex: letsencrypt failed to generate a cert), nginx will crash. The reload command usually checks for syntax errors, and it still does, but somehow systemd is still making nginx exit.
To reproduce:
- add a syntax error to a vhost
- run: systemctl reload nginx
- observe: nginx has stopped.
The systemd unit file has this:
ExecReload=/usr/sbin/nginx -g 'daemon on; master_process on;' -s reloadand if we run that command manually (as root), it works as expected (i.e. does not reload/exit when there is a syntax error).
This is more a systemd/Debian bug than Aegir, but would be curious if others are also running into this, and if anyone has ideas how to debug. For now, I duct taped around it with a custom script: https://github.com/coopsymbiotic/coopsymbiotic-ansible/commit/59c84c0869...