TriliumAlchemy - Initial CLI and rebranding for TriliumNext

[mm21]

I've recently published the initial CLI for TriliumAlchemy. It has some basic features like:

• Access Trilium configuration in a .env or .yaml file
• Tree export/import
• Database backup/restore

See the full documentation here: https://mm21.github.io/trilium-alchemy/tools/index.html

There are some more interesting features coming up like:

• Resync specified notes with specified template
  • Adds any missing child notes which are present in the template and/or reorders child notes as applicable
• Subtree dump to filesystem
  • Dumps specified subtree to filesystem, with notes stored as a .yaml metadata file (title/type/mime, attributes, child branches) and content file
  • Enables tracking of changes in source control: for example, easily determine exactly what changes you made since your last backup

Also, the project has been rebranded for TriliumNext - it will aim to keep up with any new TriliumNext features, while maintaining compatibility with Trilium.

[maphew]

This is interesting and timely. The tree export/import part especially as I've been struggling with how to keep in-app scripts in source control. Manual copy-paste circuits are tiring, so I tend to skip committing changes, which is a bad habit for me (to get back into!).

[eliandoran]

@mm21 , if you design the format that would cause as few modifications as possible for source control, it would be interesting.

The approach we took, albeit finicky, is to simply extract the ZIP and commit its contents (we already do it for the user guide and technical documentation), but we'd be interested in something nicer.

[maphew]

(the diff friendly export format) won't be as human-readable since the hierarchy won't be recreated -- just a flat structure of folders by note id

Interesting. Theoretically making an offline reference mermaid diagram, index.html, ... would be a matter of asking Trilium for the relationships of the node id's. Sidestepping clones, it seems straightforward (albeit with some effort).

[maphew]

This is really exciting to me, awakening a long held private dream - marrying Trilium's rich text editing and general webby-ness with Leo Editor's code IDE and hierarchy smarts

https://boltex.github.io/leojs/

[mm21]

@eliandoran, that sounds like a great use case. It could also be handy to import the filesystem format while preserving note ids, so you don't need to delete the tree and re-import (since Trilium creates new notes with unique ids upon zip import). I'll keep the team updated on the progress there.

@maphew, Leo looks really intriguing -- thanks for sharing. It even seems inspired by Trilium with its terminology and concept of "clones". You could maybe use JS to parse the .yaml note metadata (which will have all the parent-child relationships) from the filesystem format and recreate your whole Trilium hierarchy in Leo.

[maphew]

It even seems inspired by Trilium with its terminology and concept of "clones".

Other way around more likely, Leo Editor which LeoJS is based on, is >25 yrs old. : ) From what I've read, I think Zadam arrived at the concept independently though.