The current DockStore implementation is already known as "Repository" in the DB and config.
Thats why there should be a packages called "repository handler" which will expose a binary and named functions for easier selfhosted deployments.
There will also be a Repository app that just serves the plugins themes and more over http.
GitHub, GitLab and Gitea support will be maintained as well. Local plugins might be a bit tricky but would definitly improve development.
This change would also include an extension to the repository manifest.
The key points include thungs you currently define yourself when adding a repository. For example:
- Verification Api endpoint
- Repository type
- and future additions
Adding a repo could be smplified into just pasring a link to the file and sdvanced settings for verificarion derails (will follow repository defaults by default)
The current DockStore implementation is already known as "Repository" in the DB and config.
Thats why there should be a packages called "repository handler" which will expose a binary and named functions for easier selfhosted deployments.
There will also be a Repository app that just serves the plugins themes and more over http.
GitHub, GitLab and Gitea support will be maintained as well. Local plugins might be a bit tricky but would definitly improve development.
This change would also include an extension to the repository manifest.
The key points include thungs you currently define yourself when adding a repository. For example:
Adding a repo could be smplified into just pasring a link to the file and sdvanced settings for verificarion derails (will follow repository defaults by default)