When I’m excusing myself from Netflix (or Amazon) and chill, I’ll usually make a spoonerism and say “I’m going to greek beefly”.  Implies that a bit of Linux stuff is going on.  The other I say is beak griefly.

There you go, an insight.

So, all that I’ve done of late is kept my server, WordPress and plug-ins up to date, just maintenance stuff.  I usually go on once a week or so.

I notice that when I’m applying a WordPress update, the security setting that I used in the first place to install WordPress were too strict for WordPress to update easily.  In other words, I ask WP to update, and it says it can’t; it hasn’t the permission.  It lists all the files it couldn’t write to and rolls back the changes.

But, it only does that for new versions of old files.  I’ve noticed that when trying to add new files to directories without the right permissions, WP reports the error, fails to roll back and often breaks.

Thankfully, I use Amazon to take a snapshot of the volume that holds the websites.  By clicking about 20 clicks over 2 minutes, I perform the following steps on my virtual server

• I shut it down at the command line sudo shutdown now, then switch to the Amazon console
• I virtually disconnect the virtual SATA lead from the virtual SSD
• Virtually clone the snapshot to a new virtual SSD
• Virtually plug the virtual SATA cable in to the new virtual SSD
• Virtually press the virtual power button on the virtual front of my virtual server
• Virtually toss the old virtual SSD in the virtual incinerator

Then I log back in to the server, change the suggested directory permissions and try the WordPress upgrade again.  Given that I’ve installed three independent copies of WordPress on my server, I can create a command to fix the permissions on one, then repeat it in the other two WordPress sites.

cd /var/www/site_1
sudo chmod g+w /wp-includes/long_list_of_many_files
cd ../site_2
[keys up up enter]
cd ../site_3
[up up enter]

I think the last time I did all this, I reversed the permission changes after the upgrade was successful.  This time, I didn’t; I figure that they should have been writeable in the first place.

One other thing I’ve had a play with is Docker – I launched a new instance on Amazon just to try it out.  I don’t think I get it.  If you get the WordPress docker and install it, does it take care of MySQL, Apache, PHP, configured all neatly and ready to go?  And what if I want Nextcloud to run on the same instance?  How does that mesh with the WordPress MySQL?  Is Docker more secure?  Does it impact performance?  Do you get less customisability or control with Docker apps?  I need to read up some more.

Lastly, there was no second Linux meet the month after the first one; I forgot to follow up the meet with a recurring entry on the meetup.com site.  And there were Rail strikes that meant transport was limited.  The second will go ahead 13th December.  It’ll  mostly be a presentation, I guess, a crash course in how I made this site.

And I’ve gone off on a tangent and decided to use a wget script to download sequentially named htm files of Star Trek The Original Series episode transcripts, and scan them with grep for the phrase “I can’t do it Cap’n, I don’t have the power”.  The nearest I got was a question not from Kirk but from McCoy to Scotty.  Episode 77 The Savage Curtain

MCCOY: Can we beam the captain and Spock back up?
SCOTT: We don’t have the power. They’ll come aboard a mass of dying flesh.

There you have it.  A search online for the full phrase invariably brings up an Ace Ventura Pet Detective moment of zaniness from Jim Carey.  I downloaded the animated Star Trek transcripts and the movies and still came up with nothing closer than the above.

---

I’ve re-read some of my ‘blog today, and realised that I did the “virtual chucking out of the hard drive” shtick before, in one of my earliest posts.  Ho-hum. (Sept 2018)