server_configuration:apache [wiki.roman-halliday.com]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Apache2 Configuration ======

The configuration is built from a DigitalOcean Droplet, preconfigured with LAMP and WordPress:
  * Droplet Information: https://do.co/34TfYn8
  * The WordPress One-Click Quickstart guide: https://do.co/34TfYn8#start

===== Core configuration =====

Note: If no site is "enabled" then a default entry seems to run hosting files under: ''/var/www/html''

Site configuration file location(s):
<code bash>
# All configuration files
/etc/apache2/sites-available/

# Enabled sites
/etc/apache2/sites-enabled/
</code>

Enable/disable configurations:
<code bash>
# Disable
sudo a2dissite datablog.roman-halliday.com.conf

# Enable
sudo a2ensite datablog.roman-halliday.com.conf
</code>
===== File Ownership =====
Make sure all files are owned correctly:
<code bash>
# Site content owned by www-data so webserver can modify files
chown -R www-data:www-data /var/www

# Configuration owned by root for security
chown -R root:root /etc/apache2
</code>

===== Refresh Configuration =====
Use one of:
<code bash>
systemctl reload apache2
service apache2 reload
</code>

===== SSL - Let's Encrypt =====
SSL Encryption (the use of ''https'' over ''http'') is a bit standard now, fortunately it's become a lot easier with the addition of [[https://letsencrypt.org/|Lets Encrypt]].

  * DigitalOcean Community Documentation: [[https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-20-04|How To Secure Apache with Let's Encrypt on Ubuntu 20.04]]

If you configure the http (non secure) websites under ''/etc/apache2/sites-enabled/'', then the ''certbot'' script will leverage [[https://letsencrypt.org/|Lets Encrypt]] to create certificates, configure them and create extra configuration files for the SSL (appending ''-le-ssl'' to the file name) and add a redirect to the original ''.conf'' file.

<code bash>
certbot --apache
</code>

====== Troubleshooting ======

  * https://help.servmask.com/2018/10/27/how-to-increase-maximum-upload-file-size-in-wordpress/


===== PHP testing page =====

Hosting can be tested with the file:
<file php index.php>
<?php
// For backup, rename this for easy reference: php_info.php
phpinfo();
?>
</file>

===== Managing Page redirects/apache changes =====

So many problems with cache in browsers. Good to test with a browser which can have all data cleared, and do work in private browsing.

Using wget to test the apache configuration, see some extra samples and docs over at Computer Hope - Linux wget command.

<code bash>
# Run a command to get the default page, and view the http redirects as returned by the server
wget --verbose datablog.roman-halliday.com

# Reload apache configuration
sudo service apache2 reload
</code>

===== Bug: extra index =====
I had an extra ''index.html'' file from before. The old server prioritised ''php'' pages over ''php''. This one the other way around. It took time to realise the reason I was not getting one of the wiki pages working was because of the extra index.html'' file.
<code html>
<head>
        <title>Romanian - Roman-Halliday.com</title>
</head>
<body>
        <h1>Romanian</h1>
        <p>wiki will be here</p>
</body>
</code>