[1.19.0]
Update package to use TriliumNext
The original Trilium project is in maintenance mode
Migration - There are no special migration steps to migrate from a zadam/Trilium instance to a TriliumNext/Notes instance. Simply install TriliumNext/Notes as usual and it will use your existing database.
Trilium stores its data in a sqlite database file. If you open a webterminal into the app, can you check the db file with:
file /app/data/document.db
it should print something like:
/app/data/document.db: SQLite 3.x database, last written using SQLite version 3042000, writer version 2, read version 2, file counter 1, database pages 1, cookie 0, schema 0, unknown 0 encoding, version-valid-for 1
There are threads saying that running in Terminal xattr -c /path/to/app will clear the flag.
Mixed feelings about this.
hey, why not, surely devs on Trilium are legit and it's just Apple bureaucracy
err, that's a slippery slope and the protection's are there for a purpose.
hmmm, are Trilium devs not committed enough to sign their apps properly (it's not difficult compared to the rest of their dev effort, jeez, even I have an Apple developer licence.
Going to take a timeout and just use the browser interface for now.
Right, Cloudron won't be able to backup individual notes or export them since it has no clue about what's going on inside an app. Solution has to come from Trilium itself.
@nebulon Posting here the reply from project owner, in case it is useful to someone later on:
I'm wondering if it is possible to make notes protected by default?
Kind of. The protected status is "inherited" from the parent note when creating it. So if you make all notes protected then any new note created will be protected by default (since any possible parent is also protected). This applies while in protected session.
Also, can one edit the duration of a protected session (by default 10 minutes)?
Yes, in Options -> Other -> Protected session timeout
This is not related to Trilium, but the previous Ferdi maintainer (who was different from the owner), has restarted working in a fork, Ferdium.
There's no binary out, but I'm on the alpha and all is working as before for me, so I'm happy.
Link: https://github.com/ferdium/