computing:selfhostedwp
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| computing:selfhostedwp [2023/06/29 06:15] – oemb1905 | computing:selfhostedwp [2023/07/09 20:20] – oemb1905 | ||
|---|---|---|---|
| Line 15: | Line 15: | ||
| sudo apt install apache2 mariadb-server php8.2 php-common php-cgi php-cli php-zip php-mysql php-mbstring php-intl php-fpm php-curl php-gd php-imagick php-xml php-xmlrpc php-soap php-opcache php-apcu php-bcmath memcached wget unzip | sudo apt install apache2 mariadb-server php8.2 php-common php-cgi php-cli php-zip php-mysql php-mbstring php-intl php-fpm php-curl php-gd php-imagick php-xml php-xmlrpc php-soap php-opcache php-apcu php-bcmath memcached wget unzip | ||
| | | ||
| - | Sometimes dpkg can choose which version of php you want and it's not always the version you want. In those cases, you can explicitly specify the version you need as follows: | + | Sometimes dpkg can choose which version of php you want and it's not always the version you want. In those cases, you can explicitly specify the version you need. Some packages are only available |
| | | ||
| - | sudo apt-get install php8.2-{common, | + | sudo apt-get install php8.2-{common, |
| | | ||
| 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: | 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: | ||
| Line 29: | Line 29: | ||
| | | ||
| sudo apt remove libapache2-mod-php* --purge | sudo apt remove libapache2-mod-php* --purge | ||
| + | sudo apt install php8.2-fpm php8.2-cgi | ||
| sudo a2enmod ssl | sudo a2enmod ssl | ||
| sudo a2enmod headers | sudo a2enmod headers | ||
| Line 97: | Line 98: | ||
| Let's now shell into our instance and set up WordPress. | Let's now shell into our instance and set up WordPress. | ||
| - | ssh root@wordpress.com | + | ssh root@site1.com |
| - | mkdir Downloads | + | |
| - | cd ~/ | + | |
| - | mkdir wpdownload | + | |
| - | cd wpdownload | + | |
| curl -O https:// | curl -O https:// | ||
| tar xzvf latest.tar.gz | tar xzvf latest.tar.gz | ||
| - | | + | |
| - | sudo chmod 640 ~/Downloads/ | + | |
| - | cp ~/Downloads/ | + | |
| - | | + | |
| Okay, we will need the files and directories I created once we get it running. | Okay, we will need the files and directories I created once we get it running. | ||
| sudo mv ~/ | sudo mv ~/ | ||
| - | When the website is in production, use these permissions: | + | Now, create proper |
| - | sudo chown -R www-data: | + | sudo chown -R www-data: |
| sudo find / | sudo find / | ||
| sudo chmod 755 / | sudo chmod 755 / | ||
| Line 224: | Line 218: | ||
| Refresh WordPress and it should see the sftp server and allow you to make changes that way. Note: The sftp server is public and anyone can access this with proper credentials even if it not for WordPress so use a proper password and make sure your TLS configuration is working. Your instance should now be pretty solid. The only other thing you might want is more than one WordPress site subdomain, for example, site1.cooldomain.com, | Refresh WordPress and it should see the sftp server and allow you to make changes that way. Note: The sftp server is public and anyone can access this with proper credentials even if it not for WordPress so use a proper password and make sure your TLS configuration is working. Your instance should now be pretty solid. The only other thing you might want is more than one WordPress site subdomain, for example, site1.cooldomain.com, | ||
| - | --- // | + | --- // |
computing/selfhostedwp.txt · Last modified: 2023/12/16 20:33 by oemb1905
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
