Understand database storage

หมายเหตุ: บทความนี้ยังเป็นภาษาอังกฤษ เนื่องจากคำแปลภาษาไทยกำลังอยู่ระหว่างจัดทำ

Purpose

Plan capacity for the SQLite business and Designer databases.

Audience

Deployment operators and database administrators.

Prerequisites

Host access to the Docker installation and a verified backup before storage changes.

SQLite files grow automatically as records and indexes are added. There is no database-size setting to increase. Available space is controlled by the disk or VM that stores Docker volumes.

data.db contains business and framework records. designer.db contains Designer metadata and state, AI tokens, proposals, and audit records. Both databases run in WAL mode with foreign keys enabled, a 5-second busy timeout, and automatic checkpoints every 1,000 WAL pages. Settings → System Maintenance reports these values and runs integrity diagnostics.

SQLite supports one writer at a time. Do not scale EmuFramework by running multiple writer containers against the same /data volume.

The integration encryption key is not a SQLite file. It is stored at EMU_SECRET_KEY_PATH, or as .emu-secret.key beside designer.db. Keep it on persistent storage and back it up separately from .emubackup exports.

Check Docker usage

1. Run docker system df for host-wide usage.
2. Run docker volume inspect emuframework-data to locate the default Compose volume, or inspect the name set by EMU_VOLUME_NAME.
3. Monitor free space on the Docker host or Docker Desktop virtual disk.
4. Create a verified backup before changing disk or VM settings.
5. Increase the host filesystem or Docker Desktop disk image, then confirm free space.

Do not delete SQLite -wal or -shm files while the app is running. Do not run docker compose down -v unless permanent data deletion is intended.

Related topics

Backup · Docker operations