# Project directory

Source: https://www.storeframe.io/docs/infrastructure/architecture/docker-context

How your environment's project directory is laid out on the VM, and what survives a container restart.

Every customer VM keeps your environment under a single project root:

```
/var/www/<subdomain>.<domain>/
├── application/    Your Magento installation (the active release)
├── deployer/       Release history and files shared between releases, such as media
├── backups/        Local database backups
└── .env            Environment settings
```

Container configuration and data are managed by StoreFrame and kept next to these folders. Don't edit them by hand, because the next platform run overwrites them. Use the Hub or [Environment file (.env)](/docs/infrastructure/architecture/env-file) instead. The one exception is a custom Varnish configuration; see [Varnish](/docs/infrastructure/stack/varnish).

## The application directory

`application/` is the Magento installation root. The platform places the application here via the Deployer tool — releases land in `deployer/releases/`, and `deployer/current` is a symlink to the active release. The `application/` directory is itself a symlink to `deployer/current`.

Magento application logs live at `application/var/log/`. These log files (for example, `exception.log` and `system.log`) are streamed to the Hub environment console in real time.

## What survives a container restart

Your database, code, media and TLS certificates are stored on the VM, outside the containers, so restarting a container never loses them.

Caches (Varnish and Redis) and temporary files do not survive a restart. They rebuild automatically on the next requests.
