This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
computing:selfhostedwp [2023/06/29 06:10] – oemb1905 | computing:selfhostedwp [2023/06/30 03:25] – oemb1905 | ||
---|---|---|---|
Line 97: | Line 97: | ||
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 136: | Line 129: | ||
apt install memcached | apt install memcached | ||
nano / | nano / | ||
+ | < | ||
a2enmod cache | a2enmod cache | ||
a2enmod expires | a2enmod expires | ||
a2enmod headers | a2enmod headers | ||
+ | a2enmod rewrite | ||
+ | |||
+ | After isntalling memcached and enabling those modules, navigate to your web root and adjust your .htaccess as follows: | ||
< | < | ||
Line 152: | Line 149: | ||
</ | </ | ||
- | Enable re-writes: | ||
- | |||
- | a2enmod rewrite | ||
< | < | ||
RewriteEngine On | RewriteEngine On | ||
Line 167: | Line 161: | ||
</ | </ | ||
</ | </ | ||
- | |||
- | Enable headers: | ||
< | < | ||
Line 225: | Line 217: | ||
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, | ||
- | --- // | + | --- // |