Docs
SupportGet Started
  • Get Started
  • Platform
  • Products
  • Tutorials
  • Enterprise
  • Products
  • Backend Capsule
    • Build and Deploy
    • Configure
    • Scale
    • Monitor
    • Logs
    • Alerting (Coming Soon)
    • Add a Procfile to a Backend Application
  • Database Capsule
    • Deploy
  • Configure
  • Scale
  • Backups
  • Monitor
  • Logs
  • Alerting (Coming Soon)
  • Migrations
  • Frontend capsule
    • Deploy
  • Configure
  • Scale
  • Monitor
  • Logs
  • Alerting (Coming Soon)
  • Custom Domains
  • Storage Capsule
    • Deploy
    • Configure
    • Scale
    • Monitor
    • Logs
    • Alerting (Coming Soon)
    • How State Works
  • Wordpress Capsule
    • Deploy
    • Configure
    • Scale
    • Monitor
    • Logs
    • Alerting (Coming Soon)
  • Enterprise Clusters
    • Overview
Powered by GitBook

© Copyright Code Capsules. All rights reserved.

On this page

Was this helpful?

Export as PDF
  1. Storage Capsule

How State Works

PreviousAlerting (Coming Soon)NextDeploy

Last updated 20 days ago

Was this helpful?

A Capsule can write to a local file system, but those files will not persist after the Capsule is restarted.

A Capsule can be thought of as a computational process that can be started and restarted. When a Capsule is started, it receives a fresh copy of the code from a GitHub repository. You can write to a Capsule in a local file system, but that file system will also start afresh when the code restarts and pulls from the GitHub repository again, so any files written to that file system will not persist when the Capsule is restarted automatically.

Instead, to have the data persist, we recommend using an external database.

Take a look at our guide to for more information.

setting up file persistence with a Data Capsule