Possibility to export DB Backups to external location

[d3v19]

Describe feature

I understand how the title might be confusing but the feature I want to request is exactly that. I put down the context first.

So I have a unique deployment system where I have multiple ephemeral instances running in different DCs in sync with each other. Now what I do is have a base db saved in a S3 bucket of sort, so whenever one instance for whatever reason goes down, and spins back up, with the db url saved in the environment variable with a custom startup script, it curls the db file and saves it to the data folder for Trilium and starts trilium. Now given that db, even if doesn't have the latest data having the sync host configured, simply syncs up with the other instances without a hitch and restores as if it never went down.

Now I understand how Trilium already has the functionality to backup the db in a scheduled way in the local filesystem. But I don't know how I should periodically push that to a bucket from within Trilium itself. I could have a custom background worker which does the job but I think it'll be a sleek and efficient solution to be done from Trilium itself. Now given this seems like a custom use case but I believe having the functionality to simply push the db to an external bucket or File server for redundancy would be an excellent feature, which would further my cause as well. This would also allow me to publish my solution as a robust Trilium deployment accessory pushing adoption.

I have more ideas for Trilium accessorizing and making it even more attractive to anyone with a Phone but that is a point to be discussed separately.

Additional Information

No response

[pano9000]

If I understand this correctly: you want to be able to have the DB backup uploaded onto an external location.
You mention S3 Bucket here, but I guess that could also be any other type of storage or protocol (SMB? NFS? FTP? Potentially even Dropbox or other Cloud Storage)
Correct me if I am wrong though :-)
Otherwise I guess the title can probably be updated to "Possibility to export DB Backups to external location"?

I like the idea in general, but IMHO think this would be ideally be realized as a plugin, for when there eventually (hopefully) will be a plugin system in place for TriliumNext - otherwise you'd end up with having to bundle a bit of extra "weight" due to all the extra clients you'd need to communicate with those services/protocols

[eliandoran]

I can only see this done as potential plugins, not planned for now.

[maphew]

Personally I'm nervous about copying db files, having had conflict and data loss issues before with other apps that saved the db on dropbox/onedrive/google-drive. It's probably best served at the db infrastructure level by adopting something like LiteFS or rqlite. My closer-to-today idea is with trilium-py export->import scripts. I've a few small experiments in that realm but haven't achieved lossless round trip yet. I think it's possible with more time and attention.

However given that fly.io makes LiteFS, getting a Trilium Next docker image running there might be a "hey, it works already!" moment for the scenario you describe.

[perfectra1n]

You can also use Kopia to synchronize a local directory (GUI or Terminal supported) to all different kinds of backup solutions. I've used it, along with Restic, to backup/restore the DB without issue.

Depending on how you have TriliumNext deployed, you could easily add Kopia to your Docker compose stack, or directly on the host.