ealab

⚠️ Warning: Experimental plugin. Please make a full backup before use and test thoroughly.
<h4>About</h4>
The WordPress ecosystem has never offered a simple solution for managing content between environments. Since its inception, one problem persists: granular deployment of content and configurations.
You develop on a test site and want to send only certain content to your production site. With existing tools, two scenarios often occur: creating duplicates… or having to overwrite the entire database. The constraints imposed by the diversity of plugin ecosystem operations have already caused several attempts to fail.
We are convinced that a solution is possible.
That’s why we designed Deploy & Sync Content: a new approach, designed to finally offer selective synchronization between your environments.
<h4>Main Features</h4>
The free version offers unidirectional synchronization (Production → Staging/Local), ideal for simply transferring your content and media between your sites.
For bidirectional synchronization and advanced features, check out the Pro version(https://wp-deployer.io/en/features).
Intelligent database merging: The plugin detects existing content to update or create it as needed. You thus maintain the consistency of your environments and avoid any loss of information.
Unidirectional synchronization (free version): Production → Staging/Local: quickly transfer your content and media between your sites.
Data conflict management: The tool identifies and allows you to resolve differences before import, ensuring updates without loss.
Automatic ID mapping: Avoid duplicates and inconsistencies related to page builders and ID references.
Preservation of content relationships: Posts, taxonomies, media and metadata remain correctly linked after each synchronization.
<h3>Terms of use and External Services</h3>
Deploy & Sync Content is free to use and relies on the following services:
<ol>
<li>
Online Configuration Service (wp-deployer.io)
<ul>
<li>Purpose: Configures and updates the export/import system. This service is optional, but recommended until alternatives are provided by the community.</li>
<li>Data Collection:
<ul>
<li>IP address of your WordPress instance</li>
<li>Production URL (from plugin settings)</li>
<li>Site URL</li>
</ul>
</li>
<li>When Used:
<ul>
<li>During plugin activation</li>
<li>For configuration updates</li>
<li>For license verification (Pro version)</li>
</ul>
</li>
<li>Security: This data is used to protect our systems from spam and malicious use</li>
<li>Privacy: Data is not shared with any business partners</li>
<li>Terms & Privacy: <a href="https://wp-deployer.io/en/general-terms-and-conditions-use-gtcu" rel="nofollow ugc">https://wp-deployer.io/en/general-terms-and-conditions-use-gtcu</a></li>
</ul>
</li>
<li>
Local Data Storage
<ul>
<li>Purpose: Temporary storage for content synchronization</li>
<li>Location: in the <code>uploads</code> directory of your WordPress installations</li>
<li>Security: Data is stored on your servers and is not transmitted to any external services</li>
</ul>
</li>
</ol>
<h3>Credits</h3>
Deploy & Sync Content is developed by EA Lab.
Deploy & Sync Content includes the plugin.json file from the WP Optimize plugin 
(GPLv2+ licensed).
Deploy & Sync Content includes various software dependencies taken from the packagist 
repository, listed in vendor and vendor-prefixed directories. Most 
of them are unaltered in functionality. The only patched library is 
 jfcherng/php-diff, which has been patched for translation and customized 
rendering.

Deploy & Sync Content

Move your content easily from your production instance to your development instance.

nicolasdra

<h3>DEPLOY WEBHOOK GITHUB ACTIONS PLUGIN</h3>
A WordPress plugin to manually trigger a deploy workflow via the Github Actions REST API after updating content.
<h3>FEATURE</h3>
Trigger a deploy workflow via Github Actions after updating content. Users with manage_capabilities are only allowed to perform the action from the the WordPress admin menu.
<h3>SETTINGS</h3>
Fill out the form with the data required on the Settings Page. Find a reference below:
OWNER: The username or organization name that owns the repository. 
REPO: The name of the repository. 
WORKFLOW_ID: You can either write the full name of your .yml file, ie. “manual-trigger-workflow.yml” or the ID of the workflow that you want to trigger. You can find the ID of a workflow by going to the “Actions” tab of your repository on GitHub, clicking on the name of the workflow, and looking at the URL of the page. The ID is the number that appears after the last forward slash in the URL. 
PERSONAL_ACCESS_TOKEN: A personal access token (PAT) with the repo scope. You can create a PAT by going to “Settings” > “Developer settings” > “Personal access tokens” in your GitHub account. 
REF: The name of your repository’s main branch. Important: At the moment the plugin is able to create a webhook for a workflow_dispatch trigger without inputs. This feature is planned for later versions.
<h3>TO DO</h3>
Add feature: accept inputs.
<h3>AUTHOR</h3>
Created by Nicolás di Rago. 
https://www.nicolasdirago.com/

Deploy & Sync Content vs Deploy Webhook Github Actions