I have compiled several extensions manually and they work fine. Yet, after compiling pgsql.so
manually, aaPanel just won't recognise its existence. The module is there and added to the php.ini
. The php-info in aaPanels php overview even shows it is loaded, yet obviously not recognised. How I compiled the modules:
cd (folder of extension)
./configure --with-php-config=/www/server/php/82/bin/php-config
make
In general, the pre-existing selection of extensions is not really great. What I do not understand in general - you offer the option to install extensions through the web interface with one mouse click. Cool so far. But why do you not add ALL the extensions that are there anyway? I mean, the folder /www/server/php/xx/src/ext
is packied with extensions. What is the difficulty to just add them to the web interface? I spent 2 hours yesterday manually compiling extensions, which would take me exactly 1.5min with apt
. That's really not so convenient. As an alternative, is aaPanel capable of reading *.so files outside the /www
realm or follow symlinks?
The case with pgsql.so
is extremely annoying, since my PHP applications cannot access Postgres through UNIX socket, while all my Python3 applications can access it. I abstained from using the Postgres coming with aaPanel but deployed Postgres 14 natively. I never use TCP/IP connections for database access - who even does that on a local machine?