Over the course of this series, I’ve installed Local by Flywheel, created and tested the default WordPress site and also accessed the local development site from the Internet.

Overall I have been very impressed with Local by Flywheel. It is a very easy installation, flexible yet simple setup and easy enough to access both internally and externally.

It would be nice, in future, to see ClassicPress available as a default install rather than having to either migrate the default WordPress one or manually replace it with ClassicPress, but that might come with time as ClassicPress grows.

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.

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:

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.

You are able to give access to people externally in order that they can view your site in Local by Flywheel. You do this from the site overview page, by clicking the Enable button at the bottom of the screen:

Dynamics GP Community

Login

Map of Visits

Disclaimer

This blog is a personal project; all opinions are my own and do not necessarily reflect those of my employer.

This blog and its content is provided "AS IS" with no warranty of any kind, either expressed or implied, made in relation to the accuracy, reliability or content of the information herein. The author shall not be liable for any direct, indirect, incidental or consequential damages arising out of the use of, or inability to use, information or opinions expressed in this site and confers no rights.

The links in this blog may lead to third-party Web sites to provide access to third-party resources to assist you in finding other services and/or technical support resources. Information at these sites may change without notice and azurecurve is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.