Storage Locations and Files
WorshipDeck follows a local-first architecture. All liturgical records, custom layouts, and media assets reside exclusively on the host computer:
| Component | Server Deployment | Desktop Installer Deployment |
|---|---|---|
| SQLite Database | ./data.db (or the path defined in DB_PATH) | %LocalAppData%\WorshipDeck\data.db |
| Media Uploads | ./uploads/ (or path defined in DATA_DIR) | %LocalAppData%\WorshipDeck\uploads\ |
| PPTX Cache | ./data/pptx-cache/ | %LocalAppData%\WorshipDeck\pptx-cache\ |
Server Environment Variables
When running WorshipDeck on a dedicated Linux or Windows server, configuration is controlled through environment variables in .env:
| Variable | Default | Description |
|---|---|---|
DB_PATH | ./data.db | Absolute or relative filesystem path to the primary SQLite database file. |
PORT | 3000 | TCP port on which the HTTP server listens for operator and congregation connections. |
LISTEN_ADDR | 0.0.0.0 (server) | Network bind interface. Desktop builds enforce 127.0.0.1 to restrict access to local processes. |
DATA_DIR | ./data | Directory housing uploaded flyers, media assets, and Bible translation JSON files. |
SYNC_ALLOWED_ORIGINS | (empty) | Comma-separated list of remote origin URLs permitted to communicate with this instance for Cloud Data Sync. |
Manual Backup and Restore
Because WorshipDeck stores all state in standard filesystem files, creating a complete backup requires no special tooling:
- Stop the WorshipDeck application or service to ensure all active database transactions are cleanly flushed to disk.
- Copy
data.dband the entireuploads/directory to an encrypted external storage drive or secure network share. - To restore on a new computer, install WorshipDeck, stop the service, and replace the newly created
data.dbanduploads/folder with your backed-up copies.
Cloud Data Sync (Experimental)
Churches running multiple WorshipDeck instances (e.g. an office planning workstation and a sanctuary presentation server) can synchronize plans under Settings → Sync:
- Origin Authorization: A server accepts sync requests only from network addresses explicitly whitelisted in its
SYNC_ALLOWED_ORIGINSenvironment variable. - Ephemeral Authentication: The initiating administrator signs into the remote instance with valid credentials; the authentication token is maintained in volatile memory and never persisted to disk.
- Conflict Resolution: When an incoming service plan collides with a locally modified service, the administrator selects from three resolution strategies: Keep Local, Use Cloud, or Save Both (which renames the incoming copy).
- Live Lock: Sync is automatically disabled while a presentation console is actively projecting slides.
Factory Reset Safeguards
If you need to decommission a computer or completely reset a test environment, open Settings → Sync and scroll to Factory Reset:
| Category | What Is Purged | What Is Preserved |
|---|---|---|
| Purged Completely | All services, liturgical rundown entries, custom announcements, and uploaded media files. | None. |
| Preserved Safely | None. | Administrator and operator accounts, system configuration settings, imported TrueType fonts, and newly re-seeded default SDAH hymnal and KJV Bible corpora. |
factory reset before executing.