Sync a platform database to Codespaces

The vip-sync-db command can sync the database of a WordPress VIP Platform environment to a codespace environment that was created with the .devcontainer/devcontainer.json file provided by WPVIP.

Targeting a VIP Platform environment with the vip-sync-db command will:

Retrieve the most recent database backup for that platform environment.
Import the database backup file to the running codespace environment.
Perform a wp search-replace operation to update all URL values in the database from the platform environment’s domain to the codespace environment’s domain.
Complete wp cache flush to clear the object cache of the codespace environment.

The vip-sync-db command be run more than once in order to update the database of the codespace environment with the most recent database backup of the targeted platform environment.

Prerequisites

A codespace environment must already be created and in a running state.
To sync a database of a VIP Platform environment to a GitHub Codespaces environment, a user must have at minimum an Org admin role or an App admin role for the environment’s application.

Limitations

The same limitations for the number and frequency of database exports apply to database syncing for Codespaces.
The size of the database to be synced is limited only by the amount of available space on the user’s local machine.
GitHub Codespaces does not support syncing databases for a WordPress multisite application that has network sites with subdomain structures for their Site Address URL values. If syncing a database with a subdomain structure, a manual search and replace operation will be necessary to update the platform domain values to the codespace domain values with a unique subdirectory (e.g. searching for site-4.example.com and replacing it with https://example-80.app.github.dev/site-4). Syncing the database of a multisite that has network sites with a subdirectory structure will in most cases complete without issue.

Environment variables for targeting a platform environment

The vip-sync-db command requires the VIP_APP_ID environment variable to be set in order to target a WPVIP Platform environment for the database sync. Target a platform environment by setting the value of VIP_APP_ID as either an application’s name alias format @<app-name>.<env> (e.g. @example-app.production) or an application’s ID alias format @<app-ID>.<env> (e.g. @8886.production) with one of the following methods:

Set the environment variable in Codespaces secrets.
Set the environment variable in the config file.
Set the environment variable when running the command.

Set the environment variable in Codespaces secrets

The VIP_APP_ID environment variable and its value can be stored as a GitHub Codespaces secret. Follow GitHub’s documentation for adding a Codespaces secret to learn more about how to use this feature.

Secret “Name”: VIP_APP_ID

Secret “Value”: The target environment’s application name alias (@<app-name>.<env>) or ID alias (@<app-ID>.<env>) .

Set environment variable in the config file

In this code example, the environment variable VIP_APP_ID is added to the .devcontainer/devcontainer.json config file and the value is set to an environment’s application name alias @example-app.production:

.devcontainer/devcontainer.json

// *****************************
// *** Environment variables ***
// *****************************
"containerEnv": {
	// Application name alias format 
	"VIP_APP_ID": "@example-app.production"
	// Application ID alias format 
    // "VIP_APP_ID": "@8886.production"
},

Set the environment variable when running the command

If the value of VIP_APP_ID is not already set in a repository’s Codespaces secrets of in a branch’s config file, the value can be set at the time the vip-sync-db command is run in the local machine’s terminal.

In this command example, the value of VIP_APP_ID is set as @example-app.production in the command line:

VIP_APP_ID=@example-app.production vip-sync-db