This is an Obsidian plugin to allow easily sideloading other plugins.
Not every plugin is going to be in the official plugin directory. If there's a plugin you want that isn't there, you would have to manually download the files and put them in the .obsidian/plugins directory under your vault. What a drag! Plugins Galore allows you to simply paste the url of a repository and it will automatically install it for you. Since Obsidian presumably doesn't know how to check for updates for these plugins, Plugins Galore also checks for updates, but only when you ask it to.
DISCLAIMER: It is not recommended to install a plugin made by someone you don't trust, so please make sure you understand the security risks of sideloading plugins before using this
Paste in the url of a plugin repo (e.g. https://github.com/plugins-galore/obsidian-plugins-galore) and then click "Install". Simple as that. After that, the plugin is installed like any other, and you can enable/disable/remove it just like any other in the regular "Community Plugins" tab in the Obsidian Settings. The repo can be installed from GitHub or any GitLab (untested) or Gitea instance.
To update plugins installed through Plugins Galore, click the "Check for updates" button, and then if there are any plugins that can be updated, you can decide which ones (if any) to update.
See also Obsidian42 - BRAT which similarly allows sideloading plugins, but is targeted more at beta-testers, whereas this plugin is meant as a way for plugin developers to easily distribute actual releases of their plugins if they don't want to be a part of the official plugin directory.
Tentative Roadmap:
- Allow users to see the plugins they've installed through Plugins Galore, and view READMEs
- Create a plugin browser to search unofficial plugin directories to find more plugins
- Give the user more control and transparency into the plugins installed
- Allow users to opt to download the source of plugins and transpile plugins themselves
We check for releases on the git server, almost identically to how Obsidian handles it themselves. I'm too lazy to write out more info right now, but if you have a question or need help, feel free to make an issue letting me know to update this section of the readme.