Skip to main content

Persistent Storage

ROFL developers may use Sapphire smart contracts for secure and consistent storage across all ROFL replicas. This storage however, is not appropriate for read/write intensive applications. For this reason ROFL has built-in support for local persistent storage with the following settings:

  • Local per-machine storage, not synchronized across other ROFL replicas.
  • Fully encrypted on the host machine.
  • Preserved during ROFL upgrades and node restarts.

This type of a storage is particularly useful for caching. Docker images defined in the compose.yaml file are automatically stored to persistent storage. This way they are fetched only the first time a ROFL app is deployed, otherwise a cached version is considered.

Additionally, a ROFL developer can also take advantage of the persistent storage. Any folder residing inside the /storage folder on the host will be made persistent.

In the example below, we use the short syntax for Compose volumes to make the .ollama home folder persistent. This way we avoid downloading ollama models each time a machine hosting the ROFL app is restarted:

compose.yaml
services:
  ollama:
    image: "docker.io/ollama/ollama"
    ports:
      - "11434:11434"
    volumes:
      - /storage/ollama:/root/.ollama
    entrypoint: ["/usr/bin/bash", "-c", "/bin/ollama serve & sleep 5; ollama pull deepseek-r1:1.5b; wait"]