Errors Starting Local by Flywheel

Local By FlywheelI fired up Local by Flywheel again recently to test some changes to a plugin; as it started I received a series of errors:

Error message

Error
Uh-oh! We ran into a hiccup when trying to start the Local Machine.
Unable to start the VM: C:Program FilesOracleVirtualBoxVBoxManage.exe startvm local-by-flywheel --type headless failed:

Continue reading “Errors Starting Local by Flywheel”

Local by Flywheel: Review

Local By FlywheelThis post is part of the series on Local by Flywheel.

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.

Local by Flywheel: Test Updated Site Works

Local By FlywheelThis 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.

Local by Flywheel: Update wp.config

Local By FlywheelThis 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:

Database tab showing connection settings

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

Local by Flywheel: Upload Own Files

Local By FlywheelThis 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:

Site Overview tab showing the open button.

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:

Windows Explorer showing the site

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

Local by Flywheel: Update Links in Database

Local By FlywheelThis 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');

Local by Flywheel: Upload Own Database

Local By FlywheelThis 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:

azurecurve Database page

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

Local by Flywheel: Migrate Site to Local by Flywheel

Local By FlywheelThis 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.

Local by Flywheel: Access Site From External Location

Local By FlywheelThis post is part of the series on Local by Flywheel.

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:

Site Overview screen

Continue reading “Local by Flywheel: Access Site From External Location”