I have a part of my vault (a folder and all its subfolders) that one of my co-workers would like to have access to, but I mainly use my vault for personal stuff and I don’t want them to access that.
I have tried various plug-ins for serving a vault as a website, sharing notes online etc. but they don’t work because of the lack of plug-in support. DataviewJS queries are essential to that part of my vault and I want them to work exactly the way they do locally. For the same reason I reckon Obsidian Publish wouldn’t work either.
I’m a Sync user, so my first intuition is to install Obsidian on their computer and create a remote copy of my vault there, then exclude all other folders within the Sync settings. From what I could gather the list of excluded folders is specific to each instance, so it shouldn’t exclude them from Sync on my other devices. But that would work for me only if I can then secure it, for example by protecting the settings with a password that only I would have, and I didn’t find a way to do that.
Somebody on this thread suggests to use a nested vault, but I’ve read elsewhere that it can cause problems. It should be possible though, on the condition that the nested vault is only accessed in read mode (meaning no one can create files, which should avoid filename issues).
Which one of these options is best, or is there another one?
Either way, I’d need a way to force Reading mode on the partial remote vault. Maybe by hiding with CSS all that pertains to editing? A way of preventing changes in the Settings would be great too, but I don’t quite see how to achieve that.