search

giuspen / cherrytree

cherrytree
https://www.giuspen.net/cherrytree/
Other
3.37k stars 459 forks source link

[Feature-Request] Multi User / Share Support #507

Open bitboy85 opened 5 years ago

bitboy85 commented 5 years ago

By now its not possible / not recommended to use a db file on a network share because it can lead to strange issues and a broken database. As a simple workaround maybe the first instance of CherryTree could set a "read-only" flag in the database so that further instances can open it read only. At closing of the first instance the flag must be removed. It should be possible to overwrite the flag in case it was not possible to remove it (App / PC crash).

strarsis commented 4 years ago

This is very important! For example, KeePass 2 Password Manager offers easy multi-user access (synchronization). In fact, it is so useful that I sometimes even put some info in there that isn't really secret.

stuporuser commented 4 years ago

I emphatically agree. Lack of built-in, multi-user capability is the only reason I can't yet use CherryTree on my team--a major loss for us. Since we have no option but to use other tools to capture all our reporting with realtime collaboration, we have actually removed CherryTree from our training curriculum and replaced it with other tools (which sync online but don't come close to CherryTree's capabilities and interface). I've been checking back here occasionally, and I'm hopeful that this feature will get attention.

luminous706 commented 1 year ago

Same here, at least Cherrytree should be locked for editing if someone has it open and another instance tries to open the same file or node. Is there such feature?