Keep AI development, staging and production separate Print

Quick answer

Use a development or staging copy for implementation, then deploy a reviewed result to production. A stage can send email, call payment services, or share a database unless it is deliberately isolated. A different hostname alone does not make an environment safe.

Apply this guidance to your website task

• Apply development isolation to WordPress
• Apply development isolation to Joomla

Before you start

Identify the live site, database, file storage, mail, scheduled jobs, payment modes, analytics, and external integrations. Keep a current backup and make sure you know which environment each credential belongs to.

What to do

1. Create a local or staging copy with a clear name and its own configuration. Sanitize customer information when a realistic dataset is unnecessary.
2. Disable or redirect real email, scheduled processing, payment capture, CRM writes, and other external actions that should not run during development.
3. Use visibly different connection aliases and environment instructions. Tell the assistant which actions are allowed in each place.
4. Before release, reconcile newer live content or orders and deploy only the intended changes. Avoid replacing a live commerce database with an older test copy.

Check the result

Verify isolation with a harmless test and check the destination of any external request. After release, test production behavior using the appropriate safe transaction or review procedure.

If something does not work

If you cannot establish whether a stage shares live resources, pause writes and ask support or the developer to inspect it. Do not rely on a banner or URL label as proof of isolation.

Related help

• Use a staging copy before changing a WordPress website
• Protect a staging website with access control before adding real data
• Preserve new orders and inquiries when planning a restore

Official references

• DDEV documentation
• Git documentation

Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.

AI editing guidance and linked workflow documentation reviewed November 2, 2026. Existing video and earlier review history retained.