2.x

Creating a bash script

Bash scripts are files containing code that tell your computer to do something.  In this instance, I want to rename a batch files in a directory.  Such as changing:
 

37351001 - BlueSpotted.jpg
37351008 -SpangledEmporer _ 0133A.jpg
37353003 -Black-Bream_3481 .jpg
37353004   -35 - Yellowfin.jpg

Instead having these files appear as:

Accessing a remote server using PEM key, and I had the following response

Currently, I have a situation where I have two repositories.  The first is where I've held the code since the beginning.  The second has come on board recently and is the client repo.  However, rather than shut the original down, I want to keep both running with the same code.  How do I synchronise them so that they contain the same thing?

Had the situation where you are running composer however, the scripts stops with a prompt?  Such as:

Currently I'm working through an app that has been abandoned by the developers.  The client was getting no response from the dev company, when they asked if I could have a look.  The app hadn't been updated for 18 months.  So of course, a product that hasn't been updated in that timeframe is going to have a suite of npm update issues / conflicts.

Running composer on a server... when running the command composer update, screen would error out.  In the site directory, composer would show 

composer --version

Composer version 1.10.24 2021-12-09 20:06:33

Whereas, the commnd

/opt/plesk/php/7.4/bin/php /usr/lib64/plesk-9.0/composer.phar --version

Composer version 2.2.5 2022-01-21 17:25:52

Ok, so composer on the server is running 2.2x.  But on my site directory, 1.x

Recently I have been investigating one of my Linux server's speed using the copy [cp] command.  This came about due to 'upgrading' the server from Centos 6 to 7.  Once I had migrated a domain, I ran the following command