search

Flow-Launcher / Flow.Launcher

:mag: Quick file search & app launcher for Windows with community-made plugins
https://flowlauncher.com
MIT License
7.66k stars 301 forks source link

User configurable plugins manifest URL for Plugin Store #2178

Open jjw24 opened 1 year ago

jjw24 commented 1 year ago

Provide the option for an user-configurable manifest URL (like an option between github, jsdelivr or user-defined) which will have the following additional benefits:

  1. it will be possible to have "unofficial" plugin communities, which means the whole ecosystem is a bit more open
  2. it will make it possible to do full integration testing of plugins: for example, before opening a PR to the manifest repository to add a new plugin, I can point my flow-launcher to my fork repository and test that a complete install/update/etc works as expected.
jjw24 commented 1 year ago

Might also be a good idea to allow two manifest urls and merge the plugins from both urls into one list. This way user can have plugins from the flow community and others hosted somewhere else.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] commented 1 year ago

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

github-actions[bot] commented 11 months ago

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] commented 11 months ago

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

github-actions[bot] commented 9 months ago

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] commented 9 months ago

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

manuelkoester commented 5 months ago

Hey!
I have to say that this would be fantastic. I have been developing some Flow Launcher plugins to interact with internal systems at my current company. Think navigation, launching, settings etc. Whenever I screenshare with colleagues or they get to look over my shoulder while I work, they always ask me what this fancy launcher thing is that I use and if they can also have it.. So far I've been sending them .zips via various methods, but it isn't the greatest as updating is very tedious.

It wouldn't really be possible for me to publish these plugins into the wild, but it would be incredible if we could add our own manifests to some user setting.

manuelkoester commented 5 months ago

Hey! Just looking at this again. Would this be a good issue to start with as a first time contributor? How would you like to see this implemented?

VictoriousRaptor commented 4 months ago

Hey! Just looking at this again. Would this be a good issue to start with as a first time contributor? How would you like to see this implemented?

Feel free to contribute if you're interested.

jjw24 commented 1 month ago

How would you like to see this implemented?

The Plugin Store and PluginsManager plugin code is where you will do most of the changes:

  1. In the backend after loading the plugins manifest from GitHub, the code would load local/network location json file plugin manifests.
  2. After all plugin json files have been loaded, merge them together. This can then be used by the PluginsManager and the Plugin Store.
  3. In terms of UI, I think the field where users enter the additional manifest path would be in the PluginsManager. The Plugin Store would display all plugins, those hosted from flow and ones added by user.