“How does the Transactional file locking configuration, enabled by adding 'filelocking.enabled' => true in the config.php file, behave in the latest versions, considering it is a service for more than 100 users? Is it worth enabling or is it unnecessary?”
With Redis? It’s fine.
If you are running directly on the database you may run into issues though.
yes with Redis
Can someone who uses it show me the example of how it would work for users with a desktop app?
It’s not a button or feature that you can click on or enable/disable. It’s how the backend handles file access, and afaik it does it in this specific way anyway. The difference between using Redis or the database (which is what it uses if you do not install and configure Redis) is performance.
1 Like
Note that TFL is already on by default (the above option) and it’s de facto required (the option has been removed from the docs and there is a setup check to error if it’s disabled in the upcoming v31).
Are you perhaps referring to using the files_lock app?
1 Like
Yes, but I want to see an image of an alert that is given to users or how it gives them notice.
Afaik, Nextcloud doesn’t lock files or notify users when a file is already in use by another user. But maybe you could try the app @jtr mentioned. However, as far as I know, locking a file would still be a manual process, i.e. users would have to manually lock the files they are working on in the web interface.