Application (WaaS)
      Back to home
      1. Documentation
      2. Application (WaaS)

      Merging a WordPress Portfolio

      Juggling with multiple WordPress sites with varying plugin stacks? Discover how to centralize and streamline your operations using wildcloud. This guide will lead you through merging your diverse WordPress installations into wildcloud.

      Create New Version or Tenant in wildcloud

      Step 1: Log in to your wildcloud account. You’ll land on the console.

      Step 2: Choose to create either a new version (the development environment for your sites) or a new tenant (individual websites).

      For the Version:

      • Merge WP Installs: Integrate your WordPress sites into one new WP installation. Copy the plugin, theme, and language folders from your existing sites to this new WP installation in LocalWP.

      For Tenants:

      • Ensure Functional Parity: Your WordPress installations should mirror the plugins, themes, and language files of your chosen version for smooth operation.

      Configure WPCS API Connection

      Step 3: Set up a .WPCS-cli.env file in your local WP installations. Use a visual editor like Visual Studio Code and create this file in the Public folder where wp_config is located.

      Step 4: Input the following details in your .WPCS-cli.env file:

      • WPCS_DEFAULT_REGION: Choose between eu1 or us1.
      • WPCS_DEFAULT_API_KEY: Add the API key from your wildcloud application.
      • WPCS_DEFAULT_API_SECRET: Include the API secret.

      Note: Obtain API key and secret from the wildcloud Console under your product settings.

      Step 5: Check the setup by opening the site shell in LocalWP and running the following:

      • Check Node: node -v
      • Check WP CLI: wp —version
      • WPCS CLI Check: npx @WPCS.io/cli check

      Deploying to WPCS

      Step 6: Use the relevant CLI command to deploy your local WordPress installation to wildcloud.

      • To Create a Version: npx @WPCS.io/cli local deploy --name [VERSION_NAME]
      • To Create a Tenant: First, package your local WP install (npx @WPCS.io/cli local package) to create a Snapshot. Then, use npx @WPCS.io/cli tenant create [TENANT_NAME] --customSnapshotPath=[SNAPSHOT_PATH].

      Additional Commands:

      • Create a tenant using the current Production Version: npx @WPCS.io/cli tenant create [NAME]
      • List tenants if managing multiple products: npx @WPCS.io/cli tenant list

      Help: For assistance, use npx @WPCS.io/cli help.

      Exporting as Version or Tenant

      After successfully deploying your site(s) to wildcloud, you can export them either as a version (to influence other sites) or as a tenant (standalone sites).

      Export as Version:

      1. From your WordPress admin, select the Export to wildcloud as Version option.
      2. Decide on the Version name and necessary details in the modal window.
      3. Click Export.

      Export as Tenant:

      1. Choose Export to wildcloud as Tenant.
      2. Fill in the Tenant name and other details in the provided modal.
      3. Click Export.

      After successful exports, navigate back to your wildcloud panel to update the status of your version or tenant.

      Note on Automation and SaaS-like Management

      • Automated Storefront: With wildcloud, automate the sale of new websites through a storefront setup.
      • Unified Management: Manage diverse sites under a single version for streamlined updates and plugin management.

      Follow these steps to effectively merge, manage, and evolve your WordPress agency portfolio on wildcloud, embracing the efficiency of a WordPress productization. 🚀