WEBVTT

00:00:00.250 --> 00:00:05.869
Welcome to the AgenticEcom Astro ISR guide. We'll use Magento Admin to review the

00:00:05.927 --> 00:00:11.500
setup and explain the handoff to your headless storefront. This walkthrough covers stable

00:00:11.535 --> 00:00:16.272
version 1 point 0 point 3 and assumes the extension is installed.

00:00:17.322 --> 00:00:22.755
Open Stores, Configuration, Astro ISR. This module

00:00:22.802 --> 00:00:28.293
tells the storefront when Magento content changes, using purge webhooks and the configured Redis

00:00:28.351 --> 00:00:33.797
channel. Before enabling it, your developer needs to deploy a compatible webhook receiver

00:00:34.006 --> 00:00:37.245
and configure its hosting-specific cache purge.

00:00:38.295 --> 00:00:43.833
Under General Settings, Enable ISR Purging reveals the webhook fields. Astro

00:00:43.903 --> 00:00:49.545
Webhook URLs accepts one endpoint, or a comma-separated list for multiple targets.

00:00:49.940 --> 00:00:55.454
Use the receiver address provided for your storefront. The example path is api, webhook,

00:00:55.501 --> 00:00:59.239
magento-purge; it must actually exist on your deployment.

00:01:00.289 --> 00:01:05.966
Set Webhook Secret to the same secret used by the receiving Astro application. This

00:01:06.013 --> 00:01:11.620
stable release sends the secret as a Bearer token. Keep it private and configure it identically

00:01:11.690 --> 00:01:17.112
for every listed receiver. Our recording conceals secret values. Debug

00:01:17.170 --> 00:01:21.884
Logging is useful while diagnosing a problem, and should normally be off in production.

00:01:22.934 --> 00:01:28.634
Open Redis Settings. Confirm the host, port and channel used by your deployment. The

00:01:28.681 --> 00:01:34.010
default port is six three seven nine. These are infrastructure details, so use the actual

00:01:34.080 --> 00:01:39.699
connection your hosting environment provides. A Redis configuration alone does not replace

00:01:39.734 --> 00:01:41.742
the storefront webhook receiver.

00:01:42.792 --> 00:01:48.481
Save the configuration in staging. Make a controlled product or CMS change and inspect

00:01:48.527 --> 00:01:54.158
the receiver and Magento logs for the expected purge. Confirm the storefront serves the new

00:01:54.216 --> 00:01:59.707
content. Purging and prebuilding are distinct parts of the deployment, so check your storefront's

00:01:59.777 --> 00:02:05.361
refresh strategy as well. We are showing the controls here, without sending a live purge.

00:02:06.412 --> 00:02:11.753
Your next steps are to deploy the compatible receiver, match secret and redis settings,

00:02:11.927 --> 00:02:17.186
verify a controlled staging change. Use a staging store for the end-to-end check.

00:02:17.639 --> 00:02:22.968
The complete installation and integration reference is at user guides dot AgenticEcom dot

00:02:23.037 --> 00:02:23.688
net.