Tag: Local by Flywheel

This post is part of the series on Local by Flywheel.

The change to the wp.config file is the last of the changes needed to complete the migration of the live site into Local by Flywheel.

With the complete, you can access the site and test to make sure that everything has migrated correctly.

This post is part of the series on Local by Flywheel.

The final step of migrating a live site into Local by Flywheel is to change the wp.config file; this is what tells the WordPres site which database to connect and the credentials to do so.

The settings required for the wp.config file can be found on the Database tab in Local by Flywheel:

Continue reading “Local by Flywheel: Update wp.config”

This post is part of the series on Local by Flywheel.

With the database restored, the next step is to upload the files from the live site. I used FileZilla to FTP to the site and download the files.

One you have the files downloaded, they need to be copied to the Local by Flywheel version of the site. The fields are accessible using Windows Explorer. The easiest way to get to the folder, is via the Overview tab. On this tab, click the open button (arrow in circle) below the site name:

This will launch Windows Explorer to the Local Sites folder; expand the required site >> app >> public; all of the files in here can be deleted and replaced with the ones downloaded from the live site:

As well as uploading files from a live site, you could also upload the files to transfer your site from WordPress to ClassicPress.

This post is part of the series on Local by Flywheel.

In the last post of this series, I restored the database from my live blog into Local by Flywheel. The next step is to change the references in the database from my live domain address (https://www.azurecurve.co.uk/) to the one local to Local by Flywheel (azurecurve.local).

I did this by running the following SQL query against the database using mySQL Workbench:

/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (https://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
*/
UPDATE
	local.azc_options
		SET
			option_value = 
						REPLACE(
								option_value
                                , 'https://www.azurecurve.co.uk'
                                , 'http://azurecurve.local');
UPDATE
	local.azc_posts
		SET
			post_content = 
						REPLACE(
								post_content
                                , 'https://www.azurecurve.co.uk'
                                , 'http://azurecurve.local');

This post is part of the series on Local by Flywheel.

To migrate an existing site into Local by Flywheel, the first step is to restore your database. To make the backup, I used the mySQL Workbench, but many tools can be used to make and restore a backup of the database.

The first step is to backup your database from your current web host. Once you have this backup file, you need to restore it to the Local by Flywheel database.

The connection details for this database are available from the Local by Flywheel app on the Database tab:

With these details you can use mySQL Workbench to connect and restore the database.

This post is part of the series on Local by Flywheel.

Over the last few posts, I’ve installed Local by Flywheel and used it to deploy a WordPress site for local development and testing. However, it is capable of so much more than this.

The WordPress site it creates can be migrated to ClassicPress using the migration plugin so that you can test that fork of WordPress 4.9.8.

You can also load an existing site into Local by Flywheel so that you can develop and test on a replica of your site. Over the next few posts, I am going to cover the steps I used to migrate my blog.