With a little delay, I finally have a beta of my installer script for ASTPP version 5 ( on Debian 10, and 11 only at this time).
It is still in beta because while, the script itself it functioning fine, there seems to be some sort of incompatibility going on with ASTPP, and I am not sure what the cause is yet.
There are two branches, a main, and testing.
The main is the script running as it should, and a testing which will stop the script between sections so one can evaluate the output of the script to check for issues before going on to the next section of installation.
/*!50003 SET collation_connection = utf8mb4_0900_ai_ci */ ;
/*!50003 SET collation_connection = utf8mb4_unicode_520_ci */ ;
MariaDB was throwing an error when it got to those lines. After making the change which was suggested, the errors went away. Looking at the database, all the initial data seems to have been properly placed into MariaDB.
Unlikely, as I have never tested the script with Debian 10 until today. I spotted two problems because I am not using third party repos iNetrix is using.
By default, Debian 10 has iptables version 1.8.2 in its repo. There is a long time bug still in that version, thus iptables is not functioning correctly. One has to use Debian backports to install version 1.8.3.
Monit is also not in the Debian standard repos so Debian backports must again be used to install it.
Debian 11 is still not resolved. As previously mentioned, the major difference between Debian 10 and 11 is PHP v7.3 vs PHP v7.4,
Since the error is coming from the ASTPP code (source listed above), maybe you can provide some input on what sort of issues would cause the ASTPP code to throw errors?
Remember, this script only uses Debian repos, and source code available from SignalWire’s FreeSwitch, and iNetrix’s ASTPP. This way, there is no need for a SignalWire token, MySQL repos, nor Remi Repo.