Differences

This shows you the differences between two versions of the page.

--- computing:selfhostedwp [2023/06/29 04:34] – oemb1905
+++ computing:selfhostedwp [2023/06/29 04:58] – oemb1905
@@ Line 19: / Line 19: @@
   sudo apt-get install php8.2-{common,cgi,cli,zip,mysql,mbstring,intl,fpm,curl,gd,imagick,xml,xmlrpc,gpm,soap,opcache,apcu,bcmath}
-In this particular configuration, I am not using libapache2-mod-php. Instead I am using mpm_event and php-fpm. This is not necessary for many smaller instances or self-hosted scenarios. If you are new to self-hosting, then in addition to the above steps, you should do ''sudo apt install libapache2-mod-php8.x'' and ignore the fpm-based steps below.
+Apache2 will set up a 000-default.conf automatically and your host should now resolve. Be sure to set up TLS with certbot. Here's my preferred method:
+  sudo apt install certbot letsencrypt python3-certbot-apache
+  sudo certbot --authenticator standalone --installer apache -d wordpress.com --pre-hook "systemctl stop apache2" --post-hook "systemctl start apache2"
+  crontab -e
+  <30 2 * * 1 /usr/bin/certbot renew >> /var/log/le-renew.log>
+Once you have the LAMP stack setup and TLS properly configured, it's time to make some decisions on your php handler and your apache2 multi-processing module (mpm). There's extensive debate on this which you can read up on [[https://www.datadoghq.com/blog/monitoring-apache-web-server-performance/#prefork-mpm|here]]. In this tutorial, I've chosen not to use mpm_prefork and libapache2-mod-php. Instead I am using mpm_event and php-fpm. This is not necessary for many smaller instances or self-hosted scenarios. If you are new to self-hosting, simply run ''sudo apt install libapache2-mod-php8.x'' and remove the php-fpm and mpm_event steps below.
   sudo apt remove libapache2-mod-php --purge
@@ Line 44: / Line 51: @@
   </FilesMatch>
-That takes care of configuring php-fpm and mpm_event. Before proceeding, navigate to your tld.domain in a web browser and make sure that your site resolves properly. Now, to make sure that your WordPress index.php file resolves properly to display your home page, make sure to move index.php to the top priority as follows:
+That takes care of configuring php-fpm and mpm_event. Before proceeding, navigate to your tld.domain in a web browser and make sure that your site resolves properly. If it does not, then you should debug your setup. To do that, there's three tools that can help: phpmyadmin, phpinfo page, and configuration checking. Since you might optionally desire phpadmin later, let's set that up first.
-  sudo nano /etc/apache2/mods-enabled/dir.conf
-  <DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm>
-***
-Optionally, we can install phpmyadmin, and if you do, you should secure as follows:
+  sudo apt install phpmyadmin
   sudo htpasswd -c /etc/apache2/.phpmyadmin phpmyadmin
   sudo nano /usr/share/phpmyadmin/.htaccess
-Enter the following in the file that opens:
   <AuthType Basic>
   <AuthName "Restricted Files">
   <AuthUserFile /etc/apache2/.phpmyadmin>
   <Require valid-user>
+If you don't need phpmyadmin, you can optionally make a phpinfo page instead:
+  sudo nano /var/www/wordpress.com/public_html/info.php
+  sudo htpasswd -c /etc/apache2/.phpinfo phpinfo
+  sudo nano /usr/share/phpinfo/.htaccess
+  <AuthType Basic>
+  <AuthName "Restricted Files">
+  <AuthUserFile /etc/apache2/.phpinfo>
+  <Require valid-user>
+Now, to make sure that your WordPress index.php file resolves properly to display your home page, make sure to move index.php to the top priority as follows:
+  sudo nano /etc/apache2/mods-enabled/dir.conf
+  <DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm>
 Close and save the file.  Let's set up a database now for the WordPress instance:

Haack's Wiki

User Tools

Site Tools

Differences

Page Tools