Deploy Statamic without losing your content.
Statamic keeps content on disk, which makes the deploy model matter more than usual. Depfloy shares the content and uploads directories across releases, so what editors write in the control panel survives the next deploy.
- Runtime
- PHP 8.4
- Releases
- Zero-downtime symlink flip
- Rollback
- One click; rebuild depends on runtime and retained releases
content/ and public/assets are shared directories linked into each release, not copies inside it — an entry published from the control panel is still there after the next deploy.
Cache directories that should outlive a release are shared, so the first request after a deploy is not a cold one for every page.
Because the content is files, the project-files backup is the one that matters. It runs on a schedule to S3, R2, SFTP or local disk, with restore.
Statamic is the framework where a careless deploy model does the most damage, because the content is files rather than rows. Shared directories are what keep a deploy from overwriting the work published since the last one.
Statamic questions
Does this work with the flat-file setup or do I need a database? + −
What happens to entries created between deploys? + −
Can editors keep working during a deploy? + −
9 other frameworks deploy the same way.
The release model is identical; only the build steps differ.
Deploy Statamic to your own server.
7 days free, no credit card. Your servers keep running exactly as Depfloy configured them.