danielboven

This plugin can sign the webhook events sent by the Gravity Forms WebHooks Add-On to your endpoints by including a signature in each event’s <code>X-Gform-Signature</code> header. This allows you to verify that the events were sent by the Gravity Forms add-on, not by a third party. As of right now, you must verify the signatures by manually using your own solution. However, an example of a Node.js (JavaScript) implementation is linked below.
Before you can verify signatures, you need to retrieve your endpoint’s public key (more information at <a href="#how%20can%20i%20verify%20the%20signature%3F" rel="nofollow ugc">this question</a>).
This plugin uses the same keys for every form and endpoint, meaning that the same keys will be used for every signature generated.
<h3>Verification implementations</h3>
<ul>
<li>Node.js: See the example on <a href="https://github.com/danielboven/gravity-forms-webhook-signature/blob/main/examples/NODE_JS.md" rel="nofollow ugc">Github</a>.</li>
</ul>

Webhook Signature add-on for Gravity Forms

Add a signature HTTP header to webhook requests to prevent man-in-the-middle and replay attacks.

barteled

Have you ever stared at the upgrade button of your favorite plugin with a deep foreboding feeling of what lies ahead? Will this bring your live site to its knees? Or have you wanted to test your new exciting theme without prematurely showing it to the world?
Enter the Sandbox plugin. With two simple clicks an entire testing site is created using your existing hosting provider. No more copying down to a complex local test setup or living dangerously on a live site. A complete independent sandbox, unavailable to the general public and search engines, can be created quickly and simply. You can even create multiple sandboxes to test different iterations of your site.
There is not that much more to say, it’s that easy!
What can I test with this?
Pretty much anything, but here are some examples:
<ul>
<li>Plugin upgrades</li>
<li>Theme changes</li>
<li>Setting changes</li>
<li>Even full, WordPress upgrades</li>
<li>Plugin conflicts? Create a sandbox and disable one at a time.</li>
</ul>
Ok, but how does it work?
When you add a new sandbox, a couple simple parameters are required to differentiate it from other sandboxes. A status is displayed as the sandbox is being created. This can take some time depending on the size of your WordPress install.
Basic steps to creating the sandbox:
<ol>
<li>Copy the tables 
Database tables are copied to new tables with a different prefix and various data within the tables is updated to reflect the sandbox prefix.</li>
<li>Copy the files 
All files are copied to a new folder under the sandbox folder.</li>
<li>Update the configuration 
The configuration file within the sandbox is updated to support the unique sandbox database prefix.</li>
</ol>
Once activated, only your browser can get to the sandbox installation. You can return the live site at anytime by clicking the link in the notice at the top of the admin interface.
Can I use my existing developer tools to edit the sandbox?
Sure. Tools such as Dreamweaver can update the files located in the sandbox directory. A full path is available on the edit screen of the sandbox. Database files can be modified as well. All sandbox tables will have the prefix displayed on the edit screen of the sandbox.
Another beer and coffee fueled creation of <a href="http://think-bowl.com/" title="It's less of a tank and more of a bowl." rel="nofollow ugc">Think Bowl</a>

Sandbox

Create a completely independent test site using existing hosting that is only available to administrators.

Webhook Signature add-on for Gravity Forms vs Sandbox