Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Feature request) Automated Export of Trilium Note Database to Markdown Files #4707

Open
reds2006 opened this issue Mar 21, 2024 · 2 comments

Comments

@reds2006
Copy link

Describe feature

Dear Trilium Developers,

I would like to request a new feature that allows for the automated export of the entire note database from Trilium to Markdown files using crontab or a similar scheduling mechanism.

Currently, Trilium provides excellent note-taking capabilities, but there isn't a built-in feature to export the entire note database to Markdown files automatically. Markdown files are widely supported and offer compatibility with a variety of platforms and applications, making them a convenient format for backup and sharing purposes.

Having the ability to schedule automated exports through crontab or a similar tool would greatly enhance the usability and flexibility of Trilium, providing users with peace of mind regarding data backup and portability.

Thank you for considering my feature request.

Additional Information

No response

@meichthys
Copy link
Collaborator

Trilium is in maintenance mode, so large feature requests like this will not currently be considered.
You could, however use the ETAPI to script something close to this.

Alternatively, you could recommend this as a feature request in the TriliumNext fork which may implement additional features.

@zadam
Copy link
Owner

zadam commented Mar 27, 2024

ETAPI has an export: https://github.com/zadam/trilium/blob/master/src/etapi/etapi.openapi.yaml#L257

So you could create a CRON with such an export ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants