crimvo

Glad I could help clear that up some. To answer your question though, yes you and your expert should have no trouble doing this. This is very doable, and there are more than one way to do it to. So if your expert has a way he is more comfortable with, more than likely it should still work if he knows what he is doing!

Good luck!

One of the easiest ways to do this would be with an iFrame. So you can have this git repo hosted as say a subdomain, or a specific folder on your host. Then create a new page in WordPress, and in the code of that page, add the following:

<iframe src="https://www.layerthemes.com" width="420" height="315" frameborder="0" allowfullscreen="allowfullscreen"><iframe>

And replace the HTML values as needed for the applet. This way you can keep the code of this applet separate from the actual code of the site, and not make things messy.

You could also edit the page source to reference this code directly, but that would require making sure that all the resources needed by the files, have the correct path locations and permissions.

You can read more about embedding things into your WordPress site here:
https://optimizerwp.com/wordpress-embed-guide/

So the underlying “networking issues” really have to do with the domain name. Your WordPress install in a way is tied to your domain name, especially throughout your database entries.

This means to “clone” your site, you first have to setup the proper server DNS entries, and document root for the cloned site. I am not familiar with your current hosting enviroment, but usually this goes like this:

Create a domain/subdomain DNS entry at your host with a document root that is separate from your current site to clone in to. There you can just copy your site files from your main document root, to this new document root.

Then you will need to make a copy of your database. Again, not being famialar with your current database hosting, this will vary, but generally you will want to export your current live database to a .sql file. Then create a new database on your server, give the appropriate permissions to the database, then re-import that database from the .sql file you just created.

Then comes the edits to your wp-config.php file to connect to the new database, and re-associate WordPress with your new domain. So first find your database entries, and update them with the appropriate new database you just created. These entires should look like the following in the wp-config.php file:

define('DB_NAME', 'database_name_here');
define('DB_USER', 'username_here');
define('DB_PASSWORD', 'password_here');
define('DB_HOST', 'localhost');

Once you have those updated to match your new database, directly above the line in wp-config.php “/* That’s all, stop editing! Happy blogging. */” Like so:

define('RELOCATE',true);

/* That's all, stop editing! Happy blogging. */

Then you will need to check with your current host, and namecheap on how to point your new domain to the host. There are several ways to do this, and I would need to know more about your host setup, and where your domains current nameservers are pointed!

Happy to help more with this if you need it! Feel free to DM me.