Just a quick notice to mention that the development of Sympl 12 for Debian 12 ‘Bookworm’ has now begun.
There are quite a few issues to resolve before it can be sent to testing with the changes between Bullseye and Bookworm, but no major showstoppers at the moment.
However, with the upgrade to PHP8.2 in Bookworm, and the slow updates for PHP compatibility in a lot of things, I’ve specced out the systems for selectable PHP versions in Sympl on a per-domain basis, which I hope to integrate for launch.
Debian Bookworm is currently due to be released on June 10th, and we’ll be working hard to get Sympl ready for the day, and continue the streak of having Sympl available on the day of release.
4 Likes
This is great news, thanks so much for your work on this.
Tim
Just another ‘thanks’. Great news!
Progress is going fairly well so far - im at the stage where im testing the packages on a normal VM now:
There’s no packages on the Mythic Beasts repo yet (some work is needed to set up the relevant build environment and OS images), but it’s possible to install it semi-manually - send me a private message if you’d like a link to the .deb files to try on a Bookworm machine and help test.
Time for a quick update…
The unstable branch is working as expected, and packages are now available on the normal Mythic Beasts repository, and I’m expecting to push this to a new bookworm-testing branch in the next few days.
Obviously as its ‘unstable’, it’s not really ready for production usage, but if you’d like to help test, you should be able to grab the latest version of the Sympl install script and use that with the --unstable
switch to install it on a Debian Bookworm machine.
Time for another update!
The testing branch is live and seems to be working fine - there’s some more automated tests to be added, but its passed once-overs.
Development on sympl-php-configure
has started - it’ll be part of the sympl-web
package, and currently:
- Sets up the repo from deb.sury.org, with automatic updating thanks to
sympl-updater
.
- checks for a
config/php
file with a valid PHP version in it (based on available PHP versions), and if it finds one:
- Installs the relevant PHP-FPM version and configures it with normal set of modules.
- If it doesn’t already exist, creates a suitable FPM pool for it, with a selectable name via
config/php-pool
.
- Drops a flag file as
config/php-fpm
which signifies the site it should be run under FPM.
- Creates a symlink to the FPM pools socket.
- Runs
sympl-web-configure
which configures the site to use the pool, via the socket symlink.
- Cleans up any old pool files, and stops/disables instances of PHP-FPM which aren’t needed any more.
It’s a little brute-force at present and missing quite a few options, and it also needs some expanded functionality for handling php modules gracefully, but this should be able to be extended to support something like config/php-modules
where you can list any modules you want to be installed.
So far it looks like it should be fairly easy to back-port this to Sympl 10 and 11, as the changes to the legacy code are fairly minor.
If you have any suggestions for other functionality which you’d consider a must-have, please post on the Selectable PHP options topic!
1 Like