criar-staging

Clone production into a staging environment with an anonymized MariaDB instance.

Updated May 14, 2024

Search Tags:#staging #docker #anonymization #mariadb #lgpd #production clone #infrastructure runbook

Ready to run

npx skills add https://github.com/wagnerra23/oimpresso.com --skill criar-staging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: criar-staging
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/criar-staging
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill criar-staging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the operational risk and friction of preparing a homologation environment by cloning the live ERP into staging without touching production or triggering real actions.

Core Features & Use Cases

Fidelidade do clone: Replicates the full web app stack on staging.oimpresso.com with a dedicated MariaDB database and staging-specific environment configuration.
LGPD-friendly anonymized seeding: Seeds staging using an anonymized production dump and validates that no 0-PII data remains before exposing the environment.
Integrations neutralization: Prevents real billing/issuing flows by truncating certificates, tokens, and disabling external actions via staging .env configuration.
Operational guardrails: Includes a RUNBOOK and a catalog of “10 pegadinhas” to avoid common CT100/FrankenPHP/Docker pitfalls during deploy and seed.

Quick Start

Tell the AI: “Please create and seed the staging environment (staging.oimpresso.com) by replicating production on CT 100 with anonymization and integrations disabled.”

Frequently Asked Questions about criar-staging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I clone a production database for staging tests without exposing real user data?▼

To clone production safely for staging tests, you seed a dedicated MariaDB instance using an anonymized production dump. This process validates that zero personally identifiable information remains before exposing the homologation environment.

How do I prevent staging environment from triggering real billing and issuing integrations?▼

To prevent staging from triggering real billing flows, you truncate certificates and tokens then disable external actions via the staging environment configuration. This neutralizes integrations while replicating the web app stack.

What is the best way to replicate a production ERP environment to a Docker staging server?▼

The best way to replicate a production ERP to Docker staging is deploying via versioned deploy and seed scripts. This follows CT100/FrankenPHP/Docker runbook constraints to safely mirror the full web app stack.

Does creating a Docker staging clone with MariaDB require LGPD anonymization validation?▼

Yes, creating a Docker staging clone with MariaDB requires LGPD anonymization validation. The seeding process must run a zero-PII data validation check to ensure no personally identifiable information is exposed.

Why does my FrankenPHP Docker deployment fail when cloning production to staging?▼

FrankenPHP Docker deployments fail when cloning production to staging if common runbook pitfalls are ignored. Following operational guardrails and the catalog of known deploy and seed pitfalls prevents these infrastructure errors.