Infrastructure reference
Infrastructure and configuration reference for operators who need to fine-tune the platform running under their StoreFrame environments.
This chapter is for operators, agencies, and developers who need to work directly with the infrastructure running under their StoreFrame environments. Most customers never need to come here — the Hub handles day-to-day provisioning, scaling, and deployments, and Claude Code handles code-level work inside each environment.
Come here when you need to:
- Understand where servers sit in the StoreFrame topology and how they communicate
- Read or modify the environment file (
.env) for advanced customization of a customer VM - Trace what each Docker container in the containerized stack does and how volumes are wired
- Operate at the infrastructure level — backups, security configuration, environment lifecycle states
Who this chapter is for
Operators managing multiple environments or building agency workflows on top of StoreFrame. You'll use this material when provisioning goes wrong, when a customer has unusual requirements, or when you need to understand why a specific configuration was chosen.
Developers who have been granted SSH access to a customer VM and want to understand the directory layout before making changes.
Advanced users who want to customize their stack beyond what the Hub UI exposes — for example, tuning MariaDB buffer sizes, adjusting Varnish memory allocation, or configuring IP allowlists in the nginx layer.
What's covered
Architecture — How a single environment is laid out on disk: the .env configuration file and the Docker context under your project directory. Start here if you're new to working over SSH.
Stack — The containerized stack on each customer VM. What each Docker service does, how containers communicate, and what's persisted versus ephemeral.
Operations — Day-2 operational tasks: database backups, log access, Magento CLI commands, and common troubleshooting steps.
Before you start
If you're trying to solve a problem with a running environment — slow page loads, a failed deployment, an error in the Magento admin — check /docs/hub/environments first. The Hub surfaces diagnostics and one-click remediation for the most common issues. Only reach for this chapter when those tools aren't enough.