How an environment is organized
How a StoreFrame environment is organized on disk — the project directory, the configuration file, and the container layout.
This section covers how a single StoreFrame environment is laid out — the files you can read or edit over SSH, and the configuration file that drives provisioning.
What's covered
Environment file (.env) — The configuration file at the root of every environment. It is the source of truth for container versions, database connection parameters, nginx tunables, and similar settings. Most customers never touch it directly; the Hub UI changes it for you. Advanced users can edit it over SSH.
Project directory — The directory layout under /var/www/<subdomain>.<domain>/, and what survives a container restart.
What is not covered
How StoreFrame runs its own platform is not documented here. If you need information about platform behavior beyond your own environment, file a support ticket.
Infrastructure reference
Infrastructure and configuration reference for operators who need to fine-tune the platform running under their StoreFrame environments.
Environment file (.env)
The .env file that holds each environment's configuration — what it contains, where it lives, and how to work with it safely.