Hey Obsidians,
I’m excited to announce the release of my new open-source tool, Obsidian Vaults Manager (OVM)!
It allows to install, uninstall, prune, and generate reports for your favorite plugins across multiple vaults, boosting your productivity and efficiency. It’s suitable for users that tends to manage multiple vaults independently in different directories.
I’d love to hear your thoughts on this project, so please share your feedback!
Links
This sounds exciting! I’m trying to learn Obsidian to create an EMR with automation. One idea I have to improve security is to have all patient data in it’s own separate vault, completely separated from everything else. And then encrypt it. However, there is no plugin to allow one vault to use another one; I’ll be using Templater, Dataview, QuickAdd, and DBFolder for this project.
It would be amazing if someone could solve this challenge. I’m sure it could be extended to many other use case scenarios as well. Just an idea 
@HomeHeart I am glad that you found it exciting. super happy. 
I found shared idea completely relevant to ovm and it’s definition.
Just to let you know that during brainstorm session, I considered similar idea to execute a custom command on a vault or vaults. I agree this idea expands functionalities in terms of consuming vault’s data out of Obsidian environment.
I will add this feature and would be great if you let me know how’s encryption example in details and by which tool so the example will be used as a test case.
Awesome! Someone finally did the work! Syncing plugins across different vaults is really annoying. Can’t wait to see what’s next! 
Superb thanks for your message and supporting
Indeed it is an annoying workflow to keep all of em up to date and sync.
Enjoy
@HomeHeart Horay! A new ovm run command added to ovm [version >0.4.1]. You should be able to select your vault(s), archive and encrypt the content.
I mentioned few examples in README on how to use it. Let me know in case you encountered an issue.
Best,
Masoud
That is amazing, sir. Thank you!
I love your work! Well done and many thank yous! I appreciate you!
I have an idea and was wondering your thoughts. Is there anyway to propagate configuration files for plugins? Let’s say I have 15 Vaults and want to push a saved and custom config file for Note Toolbar Plugin (or similar). But I only want to push it to 8 of my 15 vaults. Plus, a custom config file for 4 more vaults for the Commander plugin.
This would be SO amazing 
Hi @HomeHeart
Thanks for your kind words and for sharing this idea! Appreciate the suggestion! 
I think the feature request is great and could be added to the project. I’ll consider it during upcoming design and architecture work.
It’d be great if you share a small sample containing your setup and config file.
I’ll get back to you in this thread with an update.
Hi @HomeHeart
The sync feature for core and custom vault configurations (including hotkeys, snippets, plugins data.json files, and other files) is already implemented in the latest pre-release. You can use the vaults sync or plugins sync command to propagate configurations across selected vaults. For details, check the documentations of commands and configuration.
I’d especially encourage you to try out the latest pre-release from the pipeline and test the sync functionality.
I’m keen to hear if it works well for your use case and gather any feedback!
Let me know if you have any questions in this issue!