admin - Network

New note by admin

v.01
!Friendica Support
#friendicaPHP-fpm Q&A @Tutorial

https://deadlink

rootname@VPShosting:~# sudo apt get update
rootname@VPShosting:~# sudo apt get upgrade
eventually
rootname@VPShosting:~# sudo apt get dist-upgrade

rootname@VPShosting:~# sudo sudo apt install php php-fpm libapache2-mod-php php-common php-gmp php-curl php-intl php-mbstring php-xmlrpc php-mysql php-gd php-imagick php-xml php-cli php-zip php-sqlite3

The following are adapted lists of modules for older versions of friendica so they can run in a PHP-fpm setup.

php8.1 php8.1-cli php8.1-common php8.1-dev php8.1-fpm php8.1-cgi libphp8.1-embed php8.1-phpdbg php8.1-readline php8.1-curl php8.1-mysql php8.1-sqlite3 php8.1-pgsql php8.1-imap imagemagick php8.1-imagick php8.1-gd memcached php8.1-memcached php8.1-memcache php8.1-opcache php-apcu php-apcu-bc php8.1-apcu php8.1-igbinary php8.1-mcrypt php8.1-bcmath php8.1-zip php8.1-bz2 xml2 php8.1-xml php8.1-tidy php8.1-xsl php8.1-intl php8.1-mbstring php8.1-pspell php8.1-ldap php8.1-soap php8.1-xmlrpc php-pear pkg-php-tools shtool dh-php dh-make php-geoip libruby
libapache2-mod-php8.1 libapache2-mod-fcgid apache2-suexec-pristine libapache2-mod-python

New note by admin

v.04

!Friendica Support
#friendica Q&A @Tutorial

https://deadlink

• separating the PHP process from the apache server
• speeding up processes by allowing to run multiple processes at the same time
• adjusting and fine tuning multiple processes depending on the capabilities of the hardware
• adjusting and fine tuning processes depending on the capabilities of the respective platforms
• enabling the use of different php versions for different domains and there for different platforms or different platform versions.
• adding access to PHP versions that are still in development and not at disposition in standard stable release of a server software which normally is designed to create a stable and reliable production environment for VPS server, enabling setups for the development of software and platforms.

rootname@VPShosting:~# sudo apt get update
rootname@VPShosting:~# sudo apt get upgrade
rootname@VPShosting:~# sudo install software-properties-common
rootname@VPShosting:~# sudo add-apt-repository ppa:ondrej/php

rootname@VPShosting:~# sudo apt install libapache2-mod-php libapache2-mod-fcgid php php-fpm php-mysql php-cgi php-cli

rootname@VPShosting:~# sudo apt install php-common php-curl php-gd php-imagick php-intl php-mbstring php-sqlite3 php-xml php-xmlrpc php-zip

rootname@VPShosting:~# sudo a2enmod proxy_fcgi setenvif
rootname@VPShosting:~# sudo a2enconf php-fpm
rootname@VPShosting:~# sudo systemctl restart apache2

rootname@VPShosting:~# sudo apt install libapache2-mod-php7.4 php7.4 php7.4-fpm php7.4-cgi php7.4-cli php7.4-mysql

rootname@VPShosting:~# sudo apt install php7.4-common php7.4-curl php7.4-gd php7.4-intl php7.4-zip php7.4-xml php7.4-xmlrpc php7.4-imagick php7.4-mbstring php7.4-sqlite3

rootname@VPShosting:~# sudo a2enconf php7.4-fpm
rootname@VPShosting:~# sudo systemctl restart apache2

  sudo update-alternatives --set php /usr/bin/php8.0
    sudo update-alternatives --set php-config /usr/bin/php-config8.0
    sudo update-alternatives --set phpdbg /usr/bin/phpdbg8.0
    sudo update-alternatives --set phpize /usr/bin/phpize8.0
    sudo update-alternatives --set phar /usr/bin/phar8.0
    sudo update-alternatives --set phar.phar /usr/bin/phar.phar8.0

New note by admin

To PHP, to PHP-fpm or both .. that's the question!

Trying to visualize the whole setup and questions regarding PHP to figure out what options are best.

Given the fact that more than one php version is installed, it is precise to tell the server what php version to use:

• for the server in general
• for the specific domain

Does update-alternatives fix this setting for the server in general when ever there is no specific option mentioned in the domain.com.conf file or does this setting over-ride/over-rule settings in domain.com.conf and/or local.config.php?
(it probably does not over-rule specific settings)

The friendica instalation help page states:

You can combine environment variables and options, but be aware that options are prioritized over environment variables.

Friendica settings
This variables [The following variables(?)] wont be used at normal Friendica runtime. Instead, they get saved into config/local.config.php.
FRIENDICA_PHP_PATH The path of the PHP binary

Can different settings in different places like:
/etc/alternatives/
/etc/apache2/sites-enabled/domain.com.conf
/var/www/domainfolder/bin/console config
and/or
crontab -e
create conflicts, slow down the server, become kind a fall back option or even create vulnerabilities?

• conflicts
  maybe
• slow down the server
  probably
• become kind a fall back option
  perhaps
• create vulnerabilities
  most likely

Can there actually be no standard setting in place at all as default php?
(probably not)

Is it possible to not define the php version in domain.com.conf and instead define it in:
/var/www/domainfolder/config/local.config.php
as
'php_path' => '/usr/bin/php.8.2/fpm'
as the php handler and in the case of the cron job call/define:
/usr/bin/php.8.2/fpm
instead of
/usr/bin/php
for the /var/www/domainfolder/bin/worker.php to use?

New note by admin

!Friendica Support !Friendica Admins

This help request is somehow solved. There were serious errores in different /etc/apache2/sites-available/defaultANDdomain.conf files introduced by hand and unchecked copy/paste practices.

Still having some troubles to get this work but at least there is some progress for now.

New note by admin

!Friendica Support

Problems with new friendica instance.
Actually the following post by @TupambAdminCom [2024.12] to the helpers forum doesn't show up in the helpers stream if I see this right but is available on the forum server:

tupambae.com/display/ccf09959-…
forum.friendi.ca/display/ccf09…

New note by admin

changed 127.0.0.1 to localhost
changed email to support the site.

New note by admin

Changed php path in local.config.php from a setting that was apparently still part of the K&T hosting setup 'php_path' => '/usr/bin/php' to /etc/php/8.1/fpm/.

The VPS server itself claims to be:

Configuration File (php.ini) Path => /etc/php/8.3/cli
Loaded Configuration File => /etc/php/8.3/cli/php.ini

New note by admin

Once the subdomain appears in your browser as a http site, you can proceed to create a let's encrypt SSL certificate for the domain.

As this is just creating a new certificate on an already existing let's encrypt registered certbot environment, this is quite fast and straight forward. The cert builds on the information created by the previous step of creating a sub.domain.org.conf file in /etc/apache2/sites-available/ and will create a new .conf file named:
sub.domain.org-le-ssl.conf

rootname@VPShosting:~$ sudo certbot --apache

Successfully deployed certificate for sub.domain.org to /etc/apache2/sites-available/sub.domain.org-le-ssl.conf
Congratulations! You have successfully enabled HTTPS on
sub.domain.org

New note by admin

Create a [sub]domain

Create the inicial folder to host the content:
rootname@VPShosting:~# mkdir /var/www/subdomainorg/

Create a index.html file to test the new subdomain:
rootname@VPShosting:~# nano /var/www/html/subdomainorg/index.html

<html>
<title>subdomainorg</title>
<h1>Welcome to sub.domain.org Website</h1>
<p>This is the first test subdomain site hosted with name-based virtual hosting</p>
</html>

Create ownership for the user www-data of the files and folders in /subdomainorg/:
rootname@VPShosting:~# chown -R www-data:www-data /var/www/subdomainorg/

Change ownership of the folder /subdomainorg/ itself to the user root:
rootname@VPShosting:~# chown root:root /var/www/subdomainorg

Create a domain registry file on the VPS server in /etc/apache2/sites-available/ for the subdomain:
rootname@VPShosting:~# nano /etc/apache2/sites-available/sub.domain.org.conf

<VirtualHost *:80>
ServerAdmin admin@sub.domain.org
ServerName sub.domain.org
DocumentRoot /var/www/subdomainorg
DirectoryIndex index.html
ErrorLog ${APACHE_LOG_DIR}/subdomainorg_error.log
CustomLog ${APACHE_LOG_DIR}/subdomainorg_access.log combined
</VirtualHost>

Register the new [sub]domain on the VPS server and restart the Apache webserver to apply the configuration changes:
rootname@VPShosting:~# a2ensite sub.domain.org
rootname@VPShosting:~# systemctl restart apache2

Register the subdomain IP with the domain registry provider using the VPS IP.
Depending on specific settings of the IP update routine, these changes can take up to a day to take effect and your subdomain index.html file should show up as expected.