Virus total is a website which can scan various things for viruses using a whole bunch of different virus scanners. I really like it for the sense of security before running some suss looking file I’ve downloaded (SourceForge constantly lets me down, every time).
The ability to scan for a file hash means I can just copy and paste the file hash (a bunch of text characters) into the search box and instantly see the scan results from the previous scan on that file (takes only seconds = ease of use).
This saves waiting for a a file to upload and be scanned. I use hashtools to create a SHA256 file hash, simply by right clicking a file and clicking Hash with Hashtools.
- Basically just followed these instructions. Thanks DigitalOcean
- I set WordPress to force SSL logins for fun (insecure wifi connections possibly?)
I particularly like being able to make a cert with several addresses with one command..
/opt/letsencrypt/letsencrypt-auto --apache -d example.net -d host.example.net
Starting from a fresh Ubuntu image;
- First I followed these instructions from digital ocean.
- Then set the timezone using these instructions. I didn’t yet add a swap partition – I’ll look into this once I’ve moved everything over. Also a firewall isn’t required as it’s set using AWS security groups.
- Then I installed WordPress.
- I then made a Snapshot of this basic system working on AWS.
- As far as having several WordPress sites I need to sort permissions to contain separate WordPress sites, this may involve the following:
These were suggested packages during apt-get. Also suhp has been recommended. Currently the WordPress root directory runs with 774 www-data www-data recursive permissions. Where user ubuntu has www-data group added.
These permissions allow updating plugins etc from the web ui.
- I set pretty permalinks using this info
-Enabling the rewrite mod
-Editing apache2.conf in /etc/apache2/ so to allow the FileInfo directive within <Directory /var/www/>
-The directory write permissions allowed me to set pretty permalinks and create a .htaccess file in the WP root automatically under the permalinks setting in WP dashboard.
- I also set a favicon using the new recommended way (Appearance -> Customize and clicking on Site Identity.)
- Using the WordPress Instructions of creating a networked WordPress installation I went with the Sub-directory option. This seems to work fine with separate domains using the WordPress MU Domain Mapping plugin.
- I installed the WordPress MU Domain Mapping using it’s recommended settings, this was easy enough considering it wasn’t officially supported for my WordPress version yet.
- I had a read though the final step in the WordPress Network instructions; referring to other material which I haven’t really used.. things like:
- I was able to get around having WordPress as the default Virtual host in Apache simply by creating a virtual host for any new domain and pointing it to the WordPress root directory.
- Setting Auto updates for WordPress core is done as guided here. (adding this line to wp-config.php)
define( 'WP_AUTO_UPDATE_CORE', true );
The above guide mentioned that critical plugin updates happen automatically. So I’ll leave it at that I guess. Lucky 13
- Add auto security updates.
- Perhaps change user home directory permissions..
sudo chmod 0750 /home/username
- Aand.. another snapshot.