arno/etesync-server
1
0
Fork 0
mirror of https://github.com/etesync/server synced 2025-02-21 12:52:09 +00:00
Code Issues Releases Wiki Activity

Add instructions for secret.txt

Pierre-Alain TORET 2020-03-30 17:57:10 +02:00
parent a1dc089eb4
commit 33c4117ac3
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Backups.md

@ -2,15 +2,23 @@ Running your own server is cool, but having backups is a must in that case.
Here is how to do it for the EteSync server, but the procedure depends on your storage backend Here is how to do it for the EteSync server, but the procedure depends on your storage backend
# Database
## SQLite3 (with the default name given by EteSync) ## SQLite3 (with the default name given by EteSync)
`sqlite3 /path/to/etesync/db.sq3 ".backup '/path/to/backups/backup_db.sq3'` `sqlite3 /path/to/etesync/db.sq3 ".backup '/path/to/backups/backup_db.sq3'`
If you want more info https://stackoverflow.com/questions/25675314/how-to-backup-sqlite-database or check the SQLite3 documentation If you want more info https://stackoverflow.com/questions/25675314/how-to-backup-sqlite-database or check the SQLite3 documentation.
## PostgreSQL ## PostgreSQL
Basically just dump your database using pg_dump (here we assume the database is called etesync) Basically just dump your database using pg_dump (here we assume the database is called etesync).
`pg_dump etesync > /path/to/backups/etesync.dump` `pg_dump etesync > /path/to/backups/etesync.dump`
If you want more info https://www.postgresql.org/docs/current/backup.html If you want more info https://www.postgresql.org/docs/current/backup.html
# secret.txt
it's not required to back this one up to backup your data, but having a backup of this file will make it easier to restore the database to a new EteSync server. This secret is essentially only used for hashing the login password. So it's not essential, but probably good to back up.
`cp /path/to/etesync/secret.txt /path/to/backups/`