2023-11-01 - Sympl is now 'architecture independent', Raspberry Pi Support returns!

For a while now, the packages for Sympl on armhf and arm64 CPU architecture, as used by the Raspberry Pi, have been at various levels of missing or broken.

While this hasn’t affected most of the Sympl packages, it did mean that the three packages with compiled code (sympl-cron with compiled C, sympl-firewall with compiled Ruby and sympl-web with compiled Go) were inconsistent and it was difficult to get a working system on the Rasberry Pi unless you had a very specific set of hardware and OS.

As these compiled elements are comparatively tiny and only take seconds to build, it made sense to instead compile and install these at install time, which means a few small extra dependencies for each install, but it means that Sympl is now ‘architecture independent’, so should run happily on any server running Debian, irrespective of the CPU architecture.

This has been a long-term goal of Sympl for some time, leveling the playing field a little and reducing the amount of work needed when it comes to maintaining things.

Sympl can also be run on less-common or older CPU architectures, like the ARM CPU in the original Rasberry Pi, new RISC-V CPUs or old x86 VMs, as well as any new architecture which may appear at a later date.

The update has been pushed out now for buster, bullseye and bookworm, and your install should automatically update in the next day or so or you can run sympl update manually.

There are no functional differences with these packages, but do let us know in the support forum (or directly if a Mythic Beasts customer) if you notice any issues!

1 Like

“This update has been pushed out now for buster, bullseye and bookworm”

That’s splendid news, but it might also be worth updating the documentation.

Under “Installing Sympl”, it says “There are a few ways of installing Sympl. You will need a server running Stretch (9) or Buster (10), and root access to the server.”

Fixed! Thanks for pointing that out!

A post was split to a new topic: Problem with zz-mass-hosting.ssl.conf

I’ve just pushed out a small fix for a bug which only affected new installs, properly enabling the SSL Stapling for Apache, which was missing but needed for normal SSL certificates.

Existing installs shouldn’t have been affected, as this would have already been enabled.