Copying WordPress has never seemed easy

I often like to launch a new WordPress website based on an existing website as a template. Configuration of themes, plugins, and settings is useful right from the start, unlike a fresh install where you have to repeat everything from scratch.

In Building an application image for resale on Digital Ocean, I detail the process of building an installable, pre-configured, and pre-optimized WordPress droplet. Essentially, it is a digital ocean of images that can launch a fully loaded WordPress website in minutes. More commonly, however, I want to add a WordPress website to one of my own existing servers.

There are many ways to do this, but I often find that they require a specific and detailed approach that I seem to have to relearn each time. I decided it was time to write a Linux shell script that would do all the work for me in a matter of minutes.

In this tutorial, I'll walk you through my research and generated WordPress clone script. I hope you like it - when I finished it I thought it worked pretty well.

Before we begin, please keep in mind that I do try to engage in the discussion below. If you have questions or topic suggestions, please leave a comment below or contact me on Twitter @reifman. You can also email me directly. I hope many of you will have better ideas and improvements to this script. I'm happy to hear from you.

Other Methods for WordPress Migration

Typically, you launch a new website by migrating your existing website to a new server (essentially copying it) and building on the copy while keeping the source website intact. There are several ways to achieve this.

In Migrating WordPress to a New Server Release with WordPress , I wrote about using the Duplicator plugin to do this, but I found the process cumbersome. It was also difficult to reacquaint myself with the replicator every time I needed to move the site.

I recently wrote about this in Backing up and restoring your WordPress site with CodeGuard for Envato Tuts+ . This service makes the process easier. Soon, we will publish How to Simplify Managing Multiple WordPress Websites , which describes the many powerful advantages of using ManageWP. It has cloning capabilities, but requires FTP — I avoid running FTP on my server for security reasons.

Also in Rachel McCollin’s two-part Envato Tuts+ series: Mobile WordPress: An Introduction and Mobile WordPress: Moving Your Site with Plugins. There is a tutorial on using BackupBuddy on WPBeginner. Finally, WPClone does not require FTP, but does require a clean WordPress installation to build.

You can learn a lot from all of these tutorials and services, but I wanted to see if I could create a command line script that would make cloning a WordPress site faster and easier every time.

Planning script

To write this tutorial, I relied heavily on other people's earlier work to get up to speed on bash scripting and WordPress website operations. I have never considered myself a professional Linux system administrator. Ultimately, I decided to build my clone script on top of Brian Gallagher's WordPress Bash installation script.

Note: These are Debian-based installation scripts; other versions of Linux (such as RedHat and CentOS) have different paths for Apache and different utilities.

Here's Gallagher's description of his basic script:

Download the latest WP version, update wp-config with the database name, username and password provided by the user, create and CHMOD the upload directory, copy all files to the root of the running script, and then delete itself!

There are a lot of well organized scripts out there, but I wanted to make something that would clone the live site. Let’s review the architecture of a typical WordPress configuration.

Initial components of a WordPress website

A typical WordPress installation has four main components for cloning:

1. Directory tree of website
2. database
3. Network server configuration, such as Apache configuration file
4. Domain Mapping

We also need information, access rights and security settings:

• Server management account and password
• MySql server username and password
• Source directory of the website
• Web server configuration file of the website
• Database name, username and password

Here's what we need to specify for the cloned site:

• Target directory for cloning website
• Clone database name, username and password
• Clone the web server configuration file of the website

What does the script need to do

• Get all settings via configuration variables or user input.
• Copy the website directory and restore it to the target directory.
• Export the source database and import it into the target database.
• Make sure these directories have appropriate permissions.

• Copy the server configuration file and update domain and directory settings.
• Reload the web server.

We must manually update the DNS for the new target domain. I recommend that you create DNS records before you start so that they are ready to go once you clone your website. There's nothing better than cloning your site and not being able to test the domain name because you're waiting for DNS.

Implementation method of cloning script

Now, we're ready to step through how the script's architecture works. Again, I first utilized Gallagher's WordPress installation script, and you need the initial bash line at the top:

#!/bin/bash -e
# Clone a WordPress site via Bash script
clear
echo "==================================================="
echo "Clone WordPress Script"
echo "==================================================="

Prepare your DNS settings

Before copying the site, you need to configure DNS for the cloned site. You can read about DNS configuration for a new WordPress site here. I’m also excited about this Envato Tuts+ tutorial “Introduction to Learning and Using DNS Records.”

Basically, you need to create an A record or CNAME that routes the desired clone URL to the server we are replicating to.

Setting permissions

On my server, I'm creating a bash script called clnewp.sh. It will require executable permissions:

chmod +x clonewp.sh

Then once it's done you can run it like this:

sudo bash clonewp.sh

I recommend running the script as sudo so you don't run into file permission issues.

Set default value

For testing purposes, I created a function that preloads the script with default settings. It helps me run tests over and over again without having to type everything in over and over again. I also think this might be useful for anyone who wants to modify the script or use it in other ways in the future.

The following are all default settings:

# Set Default Settings (helpful for testing)
default_mysql_user=$"root-admin"
default_mysql_pass=$"super-strong-password"
default_source_domain=$"gardening.io"
default_target_domain=$"cycling.io"
default_source_directory=$"/var/www/gardening"
default_target_directory=$"/var/www/cycling"
default_apache_directory=$"/etc/apache2/sites-available"
default_source_conf=$"gardening.conf"
default_target_conf=$"cycling.conf"
default_source_dbname=$"gardening"
default_source_dbuser=$"user_for_garden"
default_source_dbpass=$"pwd_garden"
default_target_dbname=$"cycling"
default_target_dbuser=$"user_for_cycling"
default_target_dbpass=$"pwd_cycling"
NOW=$(date +"%Y-%m-%d-%H%M")

I know this seems like a lot, but I find it useful to have a MySQL master user and password for database backups, database creation, and imports. However, it is also useful to have a site-specific database user and password to set target database permissions and search and replace in the wp-config.php file. It makes the final cloning process very seamless.

I use NOW timestamps to ensure that the archives we create are unique.

Request settings

The following code displays the default value to the user and allows them to accept it (press Enter) or replace it:

# Request Source Settings
read -p "Source Domain (e.g. "$default_source_domain"): " source_domain
source_domain=${source_domain:-$default_source_domain}
echo $source_domain
read -p "Source Directory (no trailing slash e.g. "$default_source_directory"): " source_directory
source_directory=${source_directory:-$default_source_directory}
echo $source_directory
read -p "Source Database Name (e.g. "$default_source_dbname"): " source_dbname
source_dbname=${source_dbname:-$default_source_dbname}
echo $source_dbname
read -p "Source Database User (e.g. "$default_source_dbuser"): " source_dbuser
source_dbuser=${source_dbuser:-$default_source_dbuser}
echo $source_dbuser
read -p "Source Database Pass (e.g. "$default_source_dbpass"): " source_dbpass
source_dbpass=${source_dbpass:-$default_source_dbpass}
echo $source_dbpass
# Request Source Settings
read -p "Source Conf File (e.g. "$default_source_conf"): " source_conf
source_conf=${source_conf:-$default_source_conf}
echo $source_conf
# Request Target Settings
read -p "Target Domain (e.g. "$default_target_domain"): " target_domain
target_domain=${target_domain:-$default_target_domain}
echo $target_domain
read -p "Target Directory (no trailing slash e.g. "$default_target_directory"): " target_directory
target_directory=${target_directory:-$default_target_directory}
echo $target_directory
read -p "Target Database Name (e.g. "$default_target_dbname"): " target_dbname
target_dbname=${target_dbname:-$default_target_dbname}
echo $target_dbname
read -p "Target Database User (e.g. "$default_target_dbuser"): " target_dbuser
target_dbuser=${target_dbuser:-$default_target_dbuser}
echo $target_dbuser
read -p "Target Database Pass (e.g. "$default_target_dbpass"): " target_dbpass
target_dbpass=${target_dbpass:-$default_target_dbpass}
echo $target_dbpass
read -p "Target Conf File (e.g. "$default_target_conf"): " target_conf
target_conf=${target_conf:-$default_target_conf}
echo $target_conf

Once we have collected all of the user's settings, we ask them if they want to get started:

echo "Clone now? (y/n)"
read -e run
if [ "$run" == n ] ; then
exit
else
echo "==================================================="
echo "WordPress Cloning is Beginning"
echo "==================================================="

Copy directory tree

Things are moving faster now. We create a tarball of the source site, create the target directory and extract the tarball there:

#backup source_directory
cd $source_directory
# add -v option to these if you want to see verbose file listings
tar -czf source_clone_$NOW.tar.gz .
#unzip clone in target directory
mkdir -p $target_directory
tar -xzf source_clone_$NOW.tar.gz -C $target_directory
#remove tarball of source
rm source_clone_$NOW.tar.gz
cd $target_directory

We also run WordPress’s standard file permissions to make sure everything is set up correctly and secure:

# Reset Directory Permissions
find $target_directory -type d -exec chmod 755 {} \;
find $target_directory -type f -exec chmod 644 {} \;

Update WP-Config file

Next, we use perl to search and replace the source database authentication with the target database information:

#set database details with perl find and replace
perl -pi -e "s/$source_dbname/$target_dbname/g" wp-config.php
perl -pi -e "s/$source_dbuser/$target_dbuser/g" wp-config.php
perl -pi -e "s/$source_dbpass/$target_dbpass/g" wp-config.php
echo "define('RELOCATE',true);" | tee -a wp-config.php
#echo "define('WP_HOME','http://$target_domain');" | tee -a wp-config.php
#echo "define('WP_SITEURL','http://$target_domain');" | tee -a wp-config.php
echo "================================"
echo "Directory duplicated"
echo "================================"

I also added the RELOCATE setting to the end of the file. If you wish, you can replace this with the static WP_HOME and WP_SITEURL settings.

Copy database

Next, we dump the database, create a new database with the permissions provided by the user, and import the database into it:

# Begin Database Duplication
# Export the database
mysqldump -u$mysql_user -p$mysql_pass $source_dbname > $target_directory/clone_$NOW.sql
# Create the target database and permissions
mysql -u$mysql_user -p$mysql_pass -e "create database $target_dbname; GRANT ALL PRIVILEGES ON $target_dbname.* TO '$target_dbuser'@'localhost' IDENTIFIED BY '$target_dbpass'"
# Import the source database into the target
mysql -u$mysql_user -p$mysql_pass $target_dbname < $target_directory/clone_$NOW.sql
echo "================================"
echo "Database duplicated"
echo "================================"

Once again I have found that it is best to use primary MySQL authentication for these activities while configuring the database settings based on the source site and single site clone settings.

Copy Web Server Configuration

Finally, we're ready to wrap things up and hit the start button. Rarely do I see such scripts take the extra step of managing a web server configuration. So I want to do that too.

I copied the source site's Apache .conf file into the cloned new .conf file. I'm using perl to do string replacement for domain and directory paths. I then activated the site using Apache and reloaded the web server:

#Activate Web Configuration
cp $default_apache_directory/$source_conf $default_apache_directory/$target_conf
#set database details with perl find and replace
perl -pi -e "s/$source_domain/$target_domain/g" $default_apache_directory/$target_conf
perl -pi -e "s|${source_directory}|${target_directory}|g" $default_apache_directory/$target_conf
a2ensite $target_conf
service apache2 reload
echo "================================"
echo "Web configuration added"
echo "================================"
echo "Clone is complete."
echo "Test at http://"$target_domain
echo "================================"
fi

And, that’s it. Here's how the script works in real life:

===================================================
Clone WordPress Script
===================================================
MySQL Master Username (e.g. root-admin): harry_potter
harry_potter
MySQL Master Password (e.g. super-strong-password): voldemoort~jenny7!
voldemoort~jenny7!
Source Domain (e.g. gardening.io): 
gardening.io
Source Directory (no trailing slash e.g. /var/www/gardening): 
/var/www/gardening
Source Database Name (e.g. gardening): database_gardening
database_gardening
Source Database User (e.g. user_for_garden): hermione
hermione
Source Database Pass (e.g. pwd_garden): !987654321abcdefgh#
!987654321abcdefgh#
Source Conf File (e.g. gardening.conf): gardening.conf
gardening.conf
Target Domain (e.g. cycling.io): 
cycling.io
Target Directory (no trailing slash e.g. /var/www/cycling): /var/www/cycling
/var/www/cycling
Target Database Name (e.g. cycling): database_cycling
database_cycling
Target Database User (e.g. user_for_cycling): hedwig
hedwig
Target Database Pass (e.g. pwd_cycling): 
pwd_for_cycling_not_hogwartz
Target Conf File (e.g. cycling.conf): 0007b-cycling.conf               
0007b-cycling.conf
Clone now? (y/n)
y
===================================================
WordPress Cloning is Beginning
===================================================
tar: .: file changed as we read it
define('RELOCATE',true);
================================
Directory duplicated
================================
================================
Database duplicated
================================
Enabling site 0007b-cycling.
To activate the new configuration, you need to run:
  service apache2 reload
 * Reloading web server apache2                                                                                     * 
================================
Web configuration added
================================
Clone is complete.
Test at http://cycling.io
================================

On my small WordPress site, copying only takes 30 to 90 seconds!

Fine printing

There are more things you need to know.

First log in directly to the path

First, to log in to the cloned website, you need to use the wp-login.php path instead of using wp-admin which redirects to the source website URL, for example http://clone.io/wp-login.php as follows picture:

Switch domain name

Since WordPress hardcodes most of the source domains in the database, I found that using the RELOCATE setting in wp-config.php can be easily updated via General > Settings. You can simply save the form with the new destination URL:

After saving the cloned target URL, you can remove RELOCATE settings-config.php from wp manually.

但是，一位同事建議您可能需要使用 InterconnectIT 的 WordPress 數(shù)據(jù)庫搜索和替換等工具。 Envato Tuts+ 中的“跨主機、服務器和 URL 遷移 WordPress”中也對此進行了記錄。

最終腳本

這是 wpclone.sh 的最終腳本 - 請隨意更改默認值：

#!/bin/bash -e
# Clone a WordPress site via Bash script
clear
echo "==================================================="
echo "Clone WordPress Script"
echo "==================================================="
# Set Default Settings (helpful for testing)
default_mysql_user=$"root-admin"
default_mysql_pass=$"super-strong-password"
default_source_domain=$"gardening.io"
default_target_domain=$"cycling.io"
default_source_directory=$"/var/www/gardening"
default_target_directory=$"/var/www/cycling"
default_apache_directory=$"/etc/apache2/sites-available"
default_source_conf=$"gardening.conf"
default_target_conf=$"cycling.conf"
default_source_dbname=$"gardening"
default_source_dbuser=$"user_for_garden"
default_source_dbpass=$"pwd_garden"
default_target_dbname=$"cycling"
default_target_dbuser=$"user_for_cycling"
default_target_dbpass=$"pwd_cycling"
NOW=$(date +"%Y-%m-%d-%H%M")

#Request MySQL Admin
read -p "MySQL Master Username (e.g. "$default_mysql_user"): " mysql_user
mysql_user=${mysql_user:-$default_mysql_user}
echo $mysql_user
read -p "MySQL Master Password (e.g. "$default_mysql_pass"): " mysql_pass
mysql_pass=${mysql_pass:-$default_mysql_pass}
echo $mysql_pass

# Request Source Settings
read -p "Source Domain (e.g. "$default_source_domain"): " source_domain
source_domain=${source_domain:-$default_source_domain}
echo $source_domain
read -p "Source Directory (no trailing slash e.g. "$default_source_directory"): " source_directory
source_directory=${source_directory:-$default_source_directory}
echo $source_directory
read -p "Source Database Name (e.g. "$default_source_dbname"): " source_dbname
source_dbname=${source_dbname:-$default_source_dbname}
echo $source_dbname
read -p "Source Database User (e.g. "$default_source_dbuser"): " source_dbuser
source_dbuser=${source_dbuser:-$default_source_dbuser}
echo $source_dbuser
read -p "Source Database Pass (e.g. "$default_source_dbpass"): " source_dbpass
source_dbpass=${source_dbpass:-$default_source_dbpass}
echo $source_dbpass
# Request Source Settings
read -p "Source Conf File (e.g. "$default_source_conf"): " source_conf
source_conf=${source_conf:-$default_source_conf}
echo $source_conf
# Request Target Settings
read -p "Target Domain (e.g. "$default_target_domain"): " target_domain
target_domain=${target_domain:-$default_target_domain}
echo $target_domain
read -p "Target Directory (no trailing slash e.g. "$default_target_directory"): " target_directory
target_directory=${target_directory:-$default_target_directory}
echo $target_directory
read -p "Target Database Name (e.g. "$default_target_dbname"): " target_dbname
target_dbname=${target_dbname:-$default_target_dbname}
echo $target_dbname
read -p "Target Database User (e.g. "$default_target_dbuser"): " target_dbuser
target_dbuser=${target_dbuser:-$default_target_dbuser}
echo $target_dbuser
read -p "Target Database Pass (e.g. "$default_target_dbpass"): " target_dbpass
target_dbpass=${target_dbpass:-$default_target_dbpass}
echo $target_dbpass
read -p "Target Conf File (e.g. "$default_target_conf"): " target_conf
target_conf=${target_conf:-$default_target_conf}
echo $target_conf
echo "Clone now? (y/n)"
read -e run
if [ "$run" == n ] ; then
exit
else
echo "==================================================="
echo "WordPress Cloning is Beginning"
echo "==================================================="
#backup source_directory
cd $source_directory
# add -v option to these if you want to see verbose file listings
tar -czf source_clone_$NOW.tar.gz .
#unzip clone in target directory
mkdir -p $target_directory
tar -xzf source_clone_$NOW.tar.gz -C $target_directory
#remove tarball of source
rm source_clone_$NOW.tar.gz
cd $target_directory
# Reset Directory Permissions
find $target_directory -type d -exec chmod 755 {} \;
find $target_directory -type f -exec chmod 644 {} \;
#set database details with perl find and replace
perl -pi -e "s/$source_dbname/$target_dbname/g" wp-config.php
perl -pi -e "s/$source_dbuser/$target_dbuser/g" wp-config.php
perl -pi -e "s/$source_dbpass/$target_dbpass/g" wp-config.php
echo "define('RELOCATE',true);" | tee -a wp-config.php
#echo "define('WP_HOME','http://$target_domain');" | tee -a wp-config.php
#echo "define('WP_SITEURL','http://$target_domain');" | tee -a wp-config.php
echo "================================"
echo "Directory duplicated"
echo "================================"
# Begin Database Duplication
# Export the database
mysqldump -u$mysql_user -p$mysql_pass $source_dbname > $target_directory/clone_$NOW.sql
# Create the target database and permissions
mysql -u$mysql_user -p$mysql_pass -e "create database $target_dbname; GRANT ALL PRIVILEGES ON $target_dbname.* TO '$target_dbuser'@'localhost' IDENTIFIED BY '$target_dbpass'"
# Import the source database into the target
mysql -u$mysql_user -p$mysql_pass $target_dbname < $target_directory/clone_$NOW.sql
echo "================================"
echo "Database duplicated"
echo "================================"
#Activate Web Configuration
cp $default_apache_directory/$source_conf $default_apache_directory/$target_conf
#set database details with perl find and replace
perl -pi -e "s/$source_domain/$target_domain/g" $default_apache_directory/$target_conf
perl -pi -e "s|${source_directory}|${target_directory}|g" $default_apache_directory/$target_conf
a2ensite $target_conf
service apache2 reload
echo "================================"
echo "Web configuration added"
echo "================================"
echo "Clone is complete."
echo "Test at http://"$target_domain
echo "================================"
fi

如果您有建議和定制，請告訴我。在下面的評論中發(fā)表您的想法。

清理以進行擴展測試

以下行可能有助于您刪除和撤消克隆的測試站點。您可以根據(jù)您的需要對其進行自定義：

  sudo rm -ifr /var/www/clone
  sudo a2dissite clone.conf 
  sudo service apache2 reload
  sudo rm /etc/apache2/sites-available/clone.conf
  mysql -u root -p -e "drop database clone;"

更改 Wp-Config.php 中的安全密鑰

您還可以通過手動替換目標站點的 wp-config.php 中的身份驗證密鑰和鹽來更好地保護您的新 WordPress 站點：

/**#@+
 * Authentication Unique Keys and Salts.
 *
 * Change these to different unique phrases!
 * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key 
service}
 * You can change these at any point in time to invalidate all existing cookies. This will force all users to have 
to log in again.
 *
 * @since 2.6.0
 */
define('AUTH_KEY',         '+9%S?YVnr%5Vr!Et4J,@9/Z^.kT_Lu~5SGwr9=|Y &D-ARSWf$mF#J_3U:/iE>-R');
define('SECURE_AUTH_KEY',  'e3Wr7%Aa7H1,f<SR[Sp&g.kJw,.)bR-9jz{uU&[R{[J]ITK8q>:!5@y:Q;c01dL ');
define('LOGGED_IN_KEY',    '1I%pW%UyjRMqy__Da)siA)+V]Ur$9uXPmxv|eBjM~-m&-<WEy&+XXb43uh8&aP+U');
define('NONCE_KEY',        'A9]+PFgvxYa^<B}_.F?9A,!&i-.b6E.I?&?U*)X.Vh+fq`SfE[XJG+MG|pg;y%Ah');
define('AUTH_SALT',        'gT (4]L{mm!|>9kC<%59rB7sbe1)jW0GCnfupJT+8z-z#%o@b|[QH=i@h|-/t!9S');
define('SECURE_AUTH_SALT', 'ON8K<,WSy8+F ~XaQpCwC8(a/{HksMh<T)QLD]s[-:yv+fx8!`<!*~mgB32X:w5k');
define('LOGGED_IN_SALT',   'vHJ%{=X6$ue>ZIo|%|cisp1R}9cJ< Rz-J;H|:O2A7$+*aGXMH!+KvD+tZ/I*U5$');
define('NONCE_SALT',       '[ytQ;C)BvgU!#>a,,g|)~EKBQUig7Uv.-8?q%lmFte,P>,]f#.}i`Wx8S+_S@&.(');
/**#@-*/

您只需訪問 https://api.wordpress.org/secret-key/1.1/salt/ 并將它們剪切并粘貼到您的 wp-config.php 文件中即可：

現(xiàn)在，如果您是 Linux 腳本純粹主義者，我將允許您更新 Gallagher 的 WordPress Bash 安裝腳本。他的腳本復制了默認的 WordPress wp-config.php，因此他可以使用可預測的源字符串來替換他的腳本生成的密鑰：

#set WP salts
perl -i -pe'
  BEGIN {
    @chars = ("a" .. "z", "A" .. "Z", 0 .. 9);
    push @chars, split //, "!@#$%^&*()-_ []{}<>~\`+=,.;:/?|";
    sub salt { join "", map $chars[ rand @chars ], 1 .. 64 }
  }
  s/put your unique phrase here/salt()/ge
' wp-config.php

我從未編寫過正則表達式來替換我們源站點的動態(tài)預先存在的 wp-config.php 文件中的鍵值。如果您決定這樣做，請在評論中分享并提前致謝。

有疑問嗎？

我非常喜歡讓這個腳本工作?；蛘?，我至少應該說我喜歡在完成后運行它。我希望我很久以前就創(chuàng)建了它，因為它非常有效和高效。我可以克隆小型 WordPress 網站，并在大約 60 秒內讓它們在我的服務器上運行。其他插件或復制選項都不是那么無縫。

如果您有任何疑問，請在下面發(fā)布?；蛘?，您可以通過 Twitter @reifman 聯(lián)系我或直接給我發(fā)電子郵件。請查看我的 Envato Tuts+ 講師頁面，查看我編寫的其他教程，例如我的創(chuàng)業(yè)系列（使用 PHP 構建您的創(chuàng)業(yè)公司）。

相關鏈接

• WordPress Bash 安裝腳本，作者：Brian Gallagher
• 移動 WordPress
• 用于完整 WordPress 備份的 Shell 腳本，作者：Konstantin Kovshenin
• CodeCanyon 上提供 WordPress 插件