Trilium Demo notes branch review and update

[maphew]

Describe feature

The Trilium Demo branch which ships with the default database should be reviewed and updated

• links to further info point to current Docs site (ex: https://triliumnext.github.io/Docs/Wiki/task-manager.html instead of https://github.com/zadam/trilium/wiki/Task-manager)
• new note types demo'd (ex: Mind Maps)

[eliandoran]

@maphew ,

new note types demo'd (ex: Mind Maps)

This point should already be addressed since the first beta which introduced the mindmap.

Do note that the demo branch is not kept up to date in your local database. The only way to see the latest demo is to start off with an empty database.

[maphew]

Do note that the demo branch is not kept up to date in your local database. The only way to see the latest demo is to start off with an empty database.

Oh! Of course. That points to an enhancement of: publishing Trilium Demo as part of the docs, but that won't work unless/until docs are served from Trilium instead of static html. Or an "import latest of this branch" mechanism, which in turn would rely on a possible future multi-database scenario.

[maphew]

https://triliumnext.github.io/Docs/Wiki/database.html#restoring-demo-notes has a procedure for fetching/restoring the demo notes outside of initial install time, but it relies on importing a .zip from stable, which doesn't currently exist.

I guess a github action will need to be created to make this archive as part of the release process?

[eliandoran]

@maphew , on our side we don't use the stable branch anymore.
You can use https://github.com/TriliumNext/Notes/blob/develop/db/demo.zip (or https://github.com/TriliumNext/Notes/raw/develop/db/demo.zip for a direct download) instead.

[pano9000]

if I may add my 2 cents here on this topic:

I am not sure if using a binary .zip file is the best way to handle the demo notes -- it is definitely easier to ship it this way for the releases, but managing it during dev - is a bit a pain in the ass:

• the actual demo notes are not versioned
• doing updates to the demo notes requires manual unzipping and zipping again
• you cannot easily check what changes really were made, (unless you manually unpack the zip and diff every single file)
• binary files can be more easily used for evil stuff :-) (e.g. the xz backdoor incident was also "introduced" via such a binary file IIRC)

So an idea here: maybe we should look into finding a way to have the demo files as actual files and only bundle them into a zip file when building for a release (or via some simple script, if required for dev testing).

what are your thoughts?

[maphew]

generally I think you're right Pano, however the demo notes are created in and with Trilium so there's always* going to be an export >> zip >> ship >> import set of activities, and associated diffing for changes. However there could be some trilium scripts made so it's less annoying (?)

* until there's a trilium-to-trilium sync-this-branch API. I don't think anyone is both itchy and knowledgeable enough to take that major project on yet