For the hosting of this wiki, my blog Rows Across The Lake and other things, I have a VM web host. Inspired by my migration efforts, I'm documenting the changes and challenges for next time.

Some useful notes from the first server are hidden away under initial_setup (access limited for security reasons).

The host I chose to use is use DigitalOcean I've been using them for some years and I'm very happy with the service and pricing. They have many options and allow you to scale to your requirements including hosting in many geographic locations.

Note: The link above is my Referral link, If you sign up using it we both win! Everyone I refer gets $100 in credit over 60 days. Once they’ve spent $25 with DigitalOcean, I'll get $25.

See:

• apache
• firewall
• email
• cron
• wiki
• sftp
• postgres
• squid

Also (for me):

• video notes

The original server was an older Ubuntu box, overdue to migrate.

Aim: Create a new Ubuntu Instance & migrate existing droplet data (WordPress) to it: https://datablog.roman-halliday.com/

Options were:

1. Create a new droplet (VM) and migrate site(s) and services:
   1. DigitalOcean Community Documentation: How To Migrate to a New Linux Server
   2. Start from scratch, build fresh without so much history/rubbish in the background
   3. So time consuming!
2. Upgrade server in place
   1. Why didn't I try this! It would have saved me a lot of time!
   2. Alternative… might have saved me hours!
   3. Didn't try
   4. Some advice suggested that the droplet might not have upgraded cleanly
   5. DigitalOcean Community Documentation: How To Upgrade to Ubuntu 20.04 Focal Fossa

I wanted to migrate the PI so I didn't have to make DNS changes, and so that I could quickly and easily switch between servers. But it wasn't to be:

• https://www.digitalocean.com/community/questions/how-to-transfer-ip-to-new-droplet
• https://www.digitalocean.com/community/questions/how-do-i-transfer-an-ip-address-between-droplets

So instead I had to make DNS changes, pointing the names to the new IPs. First prep step is to manage the Time To Live for DNS records. My TTL recommended times:

   60 seconds =  1 min   : Day and Time of migration
 3600 seconds =  1 hour  : Day(s) before migration
86400 seconds = 24 hours : Good operational normal

Following advice from:

• DigitalOcean Community Documentation: How To Migrate Linux Servers Part 1 - System Preparation

# System version
uname -r
uname -m
 
# Services & If they are running
service --status-all
#Firewall
ufw status
ufw status verbose
 
# More
service --status-all | more

Blessed are the paranoid for they test their backups

Yes I can SFTP etc… between droplets/environments, but this also serves as a backup for some time.

• Backup old using a volume: DigitalOcean Volumes
• Mount the volume: https://www.digitalocean.com/docs/volumes/how-to/mount/

Saving time (haha) by using a WordPress preconfigured droplet:

• Droplet Instructions: https://cloud.digitalocean.com/marketplace/5ba19759c472e4189b34e066?i=40c396
• Install & configure: The WordPress One-Click Quickstart guide: https://do.co/34TfYn8#start

As root

# create a user for me
adduser david
 
# Add my user to sudo
groupadd david sudo

# Update
sudo apt-get update && sudo apt-get upgrade

Basic SFTP was already available/configured in the box.

Worth looking at more detailed notes on my firewall configuration.

The firewall is already configured by DigitalOcean in my choice of droplet (Ubuntu 20.04 with WordPress). However if other services are to be added (in my case yes) the Ubuntu firewall needs to be configured. See below for some extra documentation links I referred to:

• HowTo Geek: How to Configure Ubuntu’s Built-In Firewall
• Ubuntu Documentation: Ubuntu firewall

In general, follow scripts/prompts when first SSH into droplet.

See apache for all details. By default for one WordPress instance, with no other sites or clever stuff, no other changes need to be made.

General guides

• https://wpengine.com/resources/migrate-wordpress-site/
• https://www.wpbeginner.com/wp-tutorials/how-to-move-wordpress-to-a-new-host-or-server-with-no-downtime/

This worked amazingly:

• https://wpengine.com/resources/migrate-wordpress-site/#All-in-One_WP_Migration
• https://help.servmask.com/knowledgebase/all-in-one-wp-migration-user-guide/

I had to make a change:

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

The two values need to be larger than the file size post_max_size and upload_max_filesize.

In the interface, the value which is shown as the “Maximum upload” is (for some reason) post_max_size.

Edit the .htaccess file, under: /var/www/roman-halliday.com/datablog

.htaccess

php_value upload_max_filesize 256M
php_value post_max_size 200M
php_value memory_limit 256M
php_value max_execution_time 300
php_value max_input_time 300

After upload, it' possible to delete/rename this file to reset settings to default.

WordPress is requiring FTP credentials before installing plugin

• https://wordpress.org/support/topic/wordpress-is-requiring-ftp-credentials-before-installing-plugin/

Modify file: wp-config.php to have the line:

define('FS_METHOD','direct');

chown -R ../ www-data:www-data /var/www

I didn't use as it migrated all the WordPress files and had some fun and games with registration:

• https://www.wpbeginner.com/wp-tutorials/how-to-move-wordpress-to-a-new-host-or-server-with-no-downtime/#setupduplicator
• https://snapcreek.com/duplicator/docs/quick-start/?

# Mount (if not already)
mount -o discard,defaults,noatime /dev/disk/by-id/scsi-0DO_Volume_volume-lon1-01 /mnt/volume_lon1_01
 
# Create Target
mkdir -p /var/www/roman-halliday.com/
cd /var/www/roman-halliday.com/
 
# Copy to Target
cp -R /mnt/volume_lon1_01/disk_backup/var/www/roman-halliday.com/romanian .
cp -R /mnt/volume_lon1_01/disk_backup/var/www/roman-halliday.com/wiki .
 
# Fix permissions:
chown -R ../ www-data:www-data /var/www

Other Stuff (cover fast, future blog post)
- Wiki(s)
- Mailbox
- Firewall
- Hostname -- https://www.cyberciti.biz/faq/ubuntu-change-hostname-command

Tips for OBS Studio, note aiming for things to look good in 1080p.

Check/visualise how many columns in putty output:

for n in {1..8}; do for i in {1..10}; do echo -n ${i: -1}; done; done; echo ""
for i in {1..80}; do echo -n '#'; done; echo ''
for i in {1..100}; do echo -n '#'; done; echo ''

PuTTY
- Font 20px
- Log: C:\Users\david\Documents\Hosting\PUtty Logs\

Windows Taskbar settings (so it's not shown in screen being recorded):
- Lock taskbar: Off
- Show taskbar on all displays: Off
- Move to other screen