Where Does EteSync Store Config and Data?
EteSync server reads a config file for database and media paths, with journal data in the database.
Last updated
EteSync server keeps settings in an INI style config file naming the database and media folders. Encrypted journals persist as rows in that database, unreadable without user keys. Server files stay small because clients hold the plaintext.
Deploy layouts root these differently across archives and Docker images. Environment variables override file values in containers. Back up the config with a database dump for restores.
Where EteSync stores this, by platform
[EteDir]/etesyncserver.ini
Database and media paths plus superuser settings live here. Journal rows sit in the named database. Containers override through environment.
Frequently asked questions
How do I back up EteSync?
Dump the database named in config with a copy of the INI file. Journals restore as encrypted rows. Keep user keys client side only.
Where are EteSync files on disk?
Nowhere readable. Journals encrypt client side before upload. The server stores ciphertext rows plus media blobs. Disk access reveals no content.
Notice an outdated path? Let us know.