Documentation

Connected Sites

Connected Sites

Connected Sites links a source WordPress installation to CanaryWP dashboard using our CanaryWP plugin.

Why connect a source site

A connection can provide CanaryWP with a structured source profile without requiring every workflow to begin with a full site import.

A profile can include information about:

  • WordPress
  • PHP
  • Plugins
  • Themes
  • Approved custom assets
  • Site inventory

Source profiles

A source profile describes the WordPress environment CanaryWP is evaluating.

Profiles are useful for:

  • Compatibility analysis
  • Inventory
  • Test recommendations
  • Maintenance planning
  • Comparing the source with a CanaryWP environment

Connect a WordPress site

The general connection process is:

  1. Install our CanaryWP plugin to your WordPress site.
  2. Go to Tools > CanaryWP, and click connect to CanaryWP.
  3. Login your CanaryWP account, or create a guest account to connect.
  4. Follow the configuration steps in the CanaryWP plugin.
  5. Click run test then wait for it to finish provisioning a testing environment WordPress site.
  6. Review the results in the apply updates tab, and click apply updates to apply the updates on your WordPress site.

Custom assets

Some sites include plugins, themes, or other assets that are not available through normal public WordPress metadata.

Only approve custom assets that are appropriate for the intended CanaryWP workflow.

After connecting

Review that CanaryWP reports the expected:

  • Site identity
  • WordPress version
  • PHP version
  • Plugins
  • Themes

If the profile is outdated, refresh or resend it before relying on the information for maintenance decisions.

Connection safety

Treat pairing credentials as access credentials.

Do not publish them in tickets, screenshots, documentation, source code, or public channels.

If a connection should no longer be trusted, remove or rotate it using the available connection controls.

Connected site versus imported instance

A Connected Site represents the source.

An Instance represents a CanaryWP environment.

Keeping those concepts separate makes it easier to tell whether you are inspecting production information or actually changing a testing copy.

On this page