A Digital Consulting Plus methodology
English
← Full mapCurated public summary
Index
Handbook
01DCP Flow: what it is and why it exists02How DCP Flow works03How to start a project04Kai and working with AI agents04AKai operational capabilities05Institutional Prompt Cookbook06Solution Discovery explained for humans07Architecture, stack, and technology ecosystem07ATool & MCP Registry07BHostinger MCP for DCP websites and hosting08Quality Gates, QA, security, and evidence08AQuality profiles and testing strategy09Git, branches, PRs, and multi-agent work10Deploy, release, support, and operational evolution10AContainer First and standardized host operations10BPractical Container First demo11How DCP Flow evolves12Real cases and lessons learned13How to teach DCP Flow14Practical DCP Flow use cases15End-to-end playbooks: Web and Laravel
Entry 10A71%
71%15 / 21
Entry 10APUBLIC HANDBOOK

Container First and standardized host operations

Operational convention for reproducible deployments on DCP-controlled infrastructure: Git, repo/deploy, Docker/Compose, /opt/dcp, persistence, and recovery.

Source & authority

Public explanation

PUBLIC HANDBOOK
Based on
Human Handbook 10A — Container First and standardized host operations
Related normative sources
  • NORMATIVE SOURCEStandard · Runtime Reproducibility
  • NORMATIVE SOURCEStandard · Deployment Environments
Authority
Public explanation — NON-NORMATIVE
Summary

Operational convention for reproducible deployments on DCP-controlled infrastructure: Git, repo/deploy, Docker/Compose, /opt/dcp, persistence, and recovery.

Container First is the operational default for software DCP installs and operates on Linux infrastructure it directly controls. The goal is reproducible, versioned, reconstructable deployments—not a universal Docker topology.

Git defines; the host executes

When Docker/Compose applies, the reproducible definition lives under repo/deploy/. On DCP hosts, /opt/dcp separates apps, data, backups, shared services, scripts, and host metadata to reduce drift and dependence on individual memory.

Key points
  • repo/deploy/ stores the definition.
  • /opt/dcp/apps/<project>/<environment> organizes deployments.
  • Persistent state must survive recreation.
  • Orphan services are an anti-pattern.

Container First is not Kubernetes First

Architecture remains project-specific. SaaS, managed services, serverless, static hosting, and constrained shared hosting may follow other runtime profiles. The target is reproducibility and explicit ownership, not containerization by dogma.

Key points
  • Docker topology is project-specific.
  • Development and production require isolation.
  • Backup needs verifiable restore.
  • A same-VM copy is not enough for production recovery.
Contextual glossary＋
Container First

DCP operational default for reproducible and normally containerized deployments on directly controlled Linux infrastructure, unless a documented technical exception applies.

Runtime Profile

Reproducible profile of the runtime environment required by a solution.

Deployment

Technical act of placing a version into an environment.

Operational Handoff

Explicit transfer of a system from delivery into operations and support.