Deployment Strategy

This document records deployment direction. It is not a production runbook yet.

Principles

• GitHub is the source of truth.
• main should represent reviewed repository state.
• Server deployments should be repeatable and logged.
• Production/showcase changes require explicit OPS tasks.
• Generated artifacts should not become source of truth.

Environments

• shop3.opencart.link receives OC3 development deployments.
• shop4.opencart.link is reserved for future OC4 work.
• docs.opencart.link receives generated MkDocs output.
• opencart.link is the internal product lab/showcase target.
• shop-theme.com is a future public brand site and should not be confused with docs hosting.

Future Direction

Preferred future deployment flow:

1. Merge reviewed PR to main.
2. Build required assets or docs.
3. Deploy to the correct server directory.
4. Log OPS details in the relevant issue.
5. Validate HTTP, admin/storefront, logs, and file permissions where relevant.

Not Yet Decided

• Final production deploy automation.
• Rollback procedure.
• Release packaging pipeline.
• Docs site deployment secrets.