Know where your data lives

Your Space is a folder on your device. Keep its files and their referenced attachments together when you move or back up your work.

Follow the files

One Space. Ordinary files.

• DirectoryResearch/ Space · a local folder

  • books.eidos Tables, fields, records, and views
  • notes.md Markdown notes
  • Directoryassets/

    • cover.jpg A cover image referenced by the book list

Inside books.eidos, the Books table has fields such as Title and Status. Each record represents a book. The Reading view saves its filter and layout.

When you move the data, include its referenced local files.

An .eidos file stores tables, fields, records, formulas, and saved view definitions. File fields store references: these can point to separate files or contain supported inline data. Do not assume every attachment is inside the database.

Images pasted into Markdown notes in Lite are saved in an assets/ folder beside the note. The note links to them with relative paths.

Saving is one part of recovery

Open a row to follow the data.

Save

Edit → local file

Keep current work. Eidos Lite writes committed edits to local files. In the Web Editor, check the save state.

Versions

Local files → local history

Review or restore recorded states. Enable versioning, then save useful milestones. History lives on the same device.

LAN sync

Phone ↔ paired computer

Manually sync shared Spaces over the same local network, without a cloud account. Each device keeps a local copy for offline use.

Cloud sync

This device ↔ cloud ↔ another device

Sync a Space through the cloud with an account and an eligible service plan. Local editing remains available offline.

Publish

Selected content → hosted page → reader

Share a page others can open. Republish after local edits to update the hosted page.

Backup

Whole Space → independent storage

Recover after device loss or drive failure. Include referenced attachments and check that you can restore the copy.

Versions and Sync serve different purposes from an independent backup. Local history can be lost with its drive. Sync can carry unwanted changes to another device.

Make a backup you can restore

1. Finish editing and check that changes are saved.
2. Close the Space and stop other programs that write to its files.
3. Copy the whole Space to independent storage. Include hidden history files if you need to preserve local history.
4. Open a separate restored copy. Check important records, notes, and attachments.

If a live-backup tool copies open databases, use its documented consistent snapshot method. Do not assume that copying an active SQLite database alone captures all committed work.

File Metadata Management stores custom values in physical file attributes. Check that your backup tool preserves those attributes. Copying files.eidos alone does not back them up. See file metadata portability.

When a file is locked

Close the other editor that is writing to the file, then retry. Do not remove lock or database sidecar files to force a file open. See troubleshooting.

Next: save a version.