Hi, I am curious if anyone has experience or insight on this topic. I setup a Nextcloud instance for a client last year, which is working quite smoothly for the most part. Dedicated server / good amount of resources / and I’m patching it up-to-date-latest approx 6x per year (roughly)
it is currently running latest/up to date.
most client access is via “RaiDrive” webDav client from windows workstations. This is to allow users a “Mapped drive” style access which they are familiar with while they work from home.
What I noticed today. Is that there appears to be complete absence of any ‘version control’ for all the files users manage in this manner. So for example
user Joe. Creates an excel file. Via webdav / Raidrive / mapped drive.
edits the files maybe 10 times in the day.
closes saves at end of day
next day more of the same
I would expect ideally at the least one version checkpoint for each day he has saved/closed
what I am seeing right now - is ‘no previous version’ when I drill in to the folder via web based access as his user and look at the file(s) he works with
I’m curious if
– this is a known feature, ie, you only get version control if you do web-based access, period ?
– it is a feature of how webdav is implemented / and depends on the webdav client?
– it is requirement to have more-different-better config in place which I should try to do?
– any other hints ?
Ideally if there was some way for me to make version control work with webdav it would be terribly useful
otherwise I think I need to look at implementing filesystem level snapshot / VM level backup at ~at least once if not more times per day. With ideally at least a 2-week retention window.
I’m hosting this thing as a VM on proxmox, so I’ll be able to do that. It is just kind of more-gross to do backup-and-recovery in this manner, rather than use built in version control / if there was some way to get at it that way.
so any feedback is greatly appreciated
thanks!
Tim