There isn’t too much too it and it’s not 1:1 with the issues related to symlinks that have already been described here.
There’s a folder structure: /rootfolder/year/month
At every start of a new month, a new subdir is created, so in case of August, we have a tree:
/rootfolder/2024/01
/rootfolder/2024/02
…
/rootfolder/2024/08
A solution that I had in place, created 2 symlinks just after the latest folder was created.
Let’s call them “thismonth” and “previousmonth”
In case of August, “thismonth” would point to /rootfolder/2024/08
and “previousmonth” to /rootfolder/2024/07
Symlinks were present in the /rootfolder/.links/
Windows clients that have used the share had those 2 shortcuts/links pinned so that they didn’t need to browse anything, just clicked those and saw proper folder contents.
Now Nextcloud doesn’t really handle that situation well. Symlinks aren’t synced and while I could do hardlink/bind, it’s hardly an elegant solution, as for NC it’s basically another folder to sync, so you just store the same data twice and waste disk space on the client.
What I would need is a way to pass/sync a simple relative symlink, as I don’t need to traverse to any other path, upwards in the tree or anything like that - just down.
If it cannot be done “nicely”, I’m fine with using hacks (so feel free to propose any), but it’d make my life way easier if there’s some switch/option that can be turned on to allow for symlink/shortcut handling that’s transparent to NC and doesn’t cause any sync issues.
