Global Settings

That is not relevant.

Not sure if this has been already implemented, but I would very much love if there is an option for global settings config, which is applicable to all vaults.

1 Like

Use case or problem

For someone that uses multiple vaults to separate projects, the ability to enable/disable plugins and have them maintain state per vault is awesome. The need to re-download a community plugin that you use all the time, however, makes little sense…especially when factoring in the need to update plugins.

Proposed solution

There are likely multiple ways to implement this, however a centralized local ‘community plugins’ repo that obsidian is aware of (either a database or folder repo with some sort of list that tracks which vault uses which installed plugins) and can offer symlinks to plugins that are frequently used, might be a way to implement it.

Pros:

  • Instead of having to re-download each time you make a new vault, and having to spend time updating plugins across each vault as you access it, this would save time in ‘micro-transaction’ style that eventually builds up to more time saved…a good feature for a program that seems to be all about efficiency.
  • Centralizing plugin management will make it easier/faster to dig out any plugins that become an issue across vaults due to either corruption, bad code practices/security issues, or malicious code.
  • Saves space! Yeah, I know, each plugin is only a couple hundred kb in size and hdd’s are (relatively) massive now and this is likely a non-issue for most, but for those people or organizations that do deep scans on viruses/malware etc. or run software that for whatever reason runs iterations through system folders, it could reasonably help cut down processing time for those types of programs. - Like I said, probably a non-issue for most.

Cons:

  • possible need to rewrite the way community plugins are handled.
  • easier for a ‘destructive’ plugin to damage multiple vaults

request for comment:

I’m sure there are other pros and cons to restructuring how plugins are handled, however I’ll leave it to others better versed in Obsidian, its code and how plugins are handled to hash that out in the comments.

Thank you for your time and consideration of this request.

~ D

4 Likes

Is a global setting for all Vaults still missing?

2 Likes

+1000 for this one, thanks for delivering such a great app!

Still not supported?

+10086!

It’s a little bit disappointing, that global settings is not a thing. I’m just started out with Obsidian and like it a lot so far, but I use several vaults and redoing all settings is really troublesome.

For example, I’m using customized community plugins and need to change the same settings over and over again (and redownload them first). Also, I want to see i.e. line numbers in every vault and need to activate them again and again.

I’d highly appreciate some sort of global settings to streamline my working flow and my preffered app behaviour. Even a possibility to import settings from an existing vault would be fine to me, that’d ease the trouble of ticking the same boxes for every vault already a lot.

3 Likes

As a workaround, how about using either Resilio Sync or SyncThing to keep the .obsidian folders in sync. That would probably work.

Data point to consider: I’ve tried syncing the .obsidian folder in the past using DropBox, and – for me at least – it seems to cause more problems than it solves. It does keep the plugins and settings synced, but it also syncs the workspace and cache, which in my opinion should be instance-specific. Worst of all, because .obsidian is a high-traffic folder, DropBox would often create conflicted copies of files, creating hard-to-find bugs in behavior and data.

Would excluding everything but the plugins and settings work?
For Dropbox, I guess that would mean using Selective Sync?

Yes, though I think Selective Sync only works at the folder level. I don’t think you can tell DropBox to, say, sync your .obsidian/plugins folder but not the .obsidian/workspace file. Still, it’s probably worth a shot to see if it works well for you.

:fire: But make a backup first! :fire:

I personally copy the hidden obsidian folder with my required settings to any new vault or copy back.

2 Likes

Ah that’s too bad about Dropbox.

SyncThing, which is free and open-source, does support file or folder exclusions. And plus doesn’t even need the cloud since it can just sync two folders on your local machine and run in the background at all times.

Please please please don’t pollute the home directory. Following an open-source standard and using the XDG Base Directory structure to store user-level files. Every OS has this idea as a way of avoiding home directory pollution. If Obsidian were an open source project I would expect these types of options available:

Path Description
XDG_CONFIG_HOME/obsidian User-level configuration options found in the current vault-level files appearance.json, app.json, community-plugins.json, core-plugins.json, graph.json, hotkeys.json.
XDG_DATA_HOME/obsidian This directory should hold the downloaded data for all plugins and themes. The path vault/.obsidian/plugins/... seems an inappropriate place for this data.
vault/.obsidian Vault-level overrides and extensions to those at the user level.

Optionally, having flags to override these values when calling the Obsidian binary would be helpful in creating one-off vault configurations. Something like:

$ /usr/bin/obsidian --config-dir ~/custom/obsidian/configs/ --data-dir ~/custom/obsidian/data
3 Likes

global HotKeys, please
even just a save to / load from global hotkeys woudl be enough to manage multiple vaults

I’ve read a lot of these topics to understand the developer’s rationale and I’m still confused. Per-vault settings are inane. Do we really have to write out use cases and justifications for something so obviously needed?

No, because there are hundreds of high-demand requests that many find obvious. They just need to expand their team.

I see this is still not implemented. Just created 4 new vaults and I wanted the settings from the first one copied across with plugins etc. However when i copy the .obsidian directory the new new vaults have the notes listed from the first vault which is NOT what i wanted. Which of the many files in the .obsidian directory lists the notes so i leave that one out from the copy?

They came from the recent files plugin! if i don’t copy that its fine.

1 Like