intermezzo:
Summing up right now:
On ubuntu in the case of friendica the php version the instance can or will use can be set by the conf file in:
/etc/apache2/sites-available/friendicaDomain.com.conf
or the specific friendica config file:
/var/www/friendicafolder/config/local.config.php.
In any case it's probably important to not manipulate both options but one or the other.
Could be important to have in mind what happens when the server software itself get's update or the friendica instance is updated.
In other words, one thing is if the reference goes to the general php setting of the server:
'php_path' => '/usr/bin/php'
When the server updates, the installed friendica version will have to be able to work with that newer php version.
(¿what about the recent ubuntu php update mentioned above by the ubuntu server, where exactly takes that APT check place, would an uninstall of "outdated versions" affect the general setting of different sites and php versions?)
If the friendica version get's updated but the server is stuck on an older not supported php version, there would probably occur issues too.
So one one hand there is to consider where the definition of the php path and version will be placed, on the other if the version itself should be hardcoded or left to the updates. If problems show up, in general terms the bug research does have to look the other way around, what php version is activated and where is that setting defined?
utopiArte /
npub129…2upjh
2025-03-10 23:56:10
in reply to nevent1q…kdcu
Author Public Key
npub1294khcygmzxr8fudt4dany08xnz7w3ufqqf4f835regcwpdwqamq82upjhPublished at
2025-03-10 23:56:10Event JSON
{
"id": "da7eed96bc5256954ca5d5c3281c5c63a4876a751afd76d55d76d71b3ae4ba44",
"pubkey": "516b6be088d88c33a78d5d5bd991e734c5e747890013549e341e518705ae0776",
"created_at": 1741650970,
"kind": 1,
"tags": [
[
"p",
"15b7758904cd6ec9c4d780aed7cca01019b61be45945dea8a68e2d2322a45ecd",
"wss://relay.mostr.pub"
],
[
"e",
"b90ca0b12384566cfe4af559ff1bb42fc92641560a90657f0eaff2be3c5a620d",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://tupambae.org/objects/0ac89072-4167-cf7c-1a93-b1d490845567",
"activitypub"
]
],
"content": "intermezzo:\n\nSumming up right now:\nOn ubuntu in the case of friendica the php version the instance can or will use can be set by the conf file in:\n/etc/apache2/sites-available/friendicaDomain.com.conf\nor the specific friendica config file:\n/var/www/friendicafolder/config/local.config.php.\n\nIn any case it's probably important to not manipulate both options but one or the other.\nCould be important to have in mind what happens when the server software itself get's update or the friendica instance is updated.\nIn other words, one thing is if the reference goes to the general php setting of the server:\n'php_path' =\u003e '/usr/bin/php'\nWhen the server updates, the installed friendica version will have to be able to work with that newer php version.\n(¿what about the recent ubuntu php update mentioned above by the ubuntu server, where exactly takes that APT check place, would an uninstall of \"outdated versions\" affect the general setting of different sites and php versions?)\n\nIf the friendica version get's updated but the server is stuck on an older not supported php version, there would probably occur issues too.\n\nSo one one hand there is to consider where the definition of the php path and version will be placed, on the other if the version itself should be hardcoded or left to the updates. If problems show up, in general terms the bug research does have to look the other way around, what php version is activated and where is that setting defined?",
"sig": "c005000506fc4b4eb2776ebb0fcc305d3f36fabe746aeb2a906e44ec78ea401c71c6c0e8d69d623ef52426f6f5879bf369dbceb9027aad7e1639bea0a9c68451"
}