cleanup and rename provider to plugin
This commit is contained in:
@@ -35,7 +35,7 @@ Plugins are the main integration surface for the app.
|
||||
- Plugins can expose named instances, so one plugin can target multiple endpoints, accounts, or servers via `-instance <name>`.
|
||||
- Bundled and external plugins use the same `plugins/<name>/` layout.
|
||||
- External plugin search paths include the repo `plugins/` folder, the current working directory `plugins/` folder, `MM_PLUGIN_PATH`, and `MEDEIA_PLUGIN_PATH`.
|
||||
- Plugin authoring still uses the current Python base class name `ProviderCore.base.Provider`. That is an implementation detail rather than the preferred user-facing term.
|
||||
- Plugin authoring still uses the current Python base class name `PluginCore.base.Provider`. That is an implementation detail rather than the preferred user-facing term.
|
||||
|
||||
See [plugins/README.md](plugins/README.md) for plugin packaging and discovery details.
|
||||
|
||||
@@ -140,8 +140,8 @@ The exact meaning of `@1` depends on the current table and plugin. For example,
|
||||
|
||||
- [docs/tag_template_syntax.md](docs/tag_template_syntax.md)
|
||||
- [plugins/README.md](plugins/README.md)
|
||||
- [docs/provider_guide.md](docs/provider_guide.md)
|
||||
- [docs/provider_authoring.md](docs/provider_authoring.md)
|
||||
- [docs/plugin_guide.md](docs/plugin_guide.md)
|
||||
- [docs/plugin_authoring.md](docs/plugin_authoring.md)
|
||||
- [docs/ftp_plugin_tutorial.md](docs/ftp_plugin_tutorial.md)
|
||||
- [docs/scp_plugin_tutorial.md](docs/scp_plugin_tutorial.md)
|
||||
- [docs/BOOTSTRAP_TROUBLESHOOTING.md](docs/BOOTSTRAP_TROUBLESHOOTING.md)
|
||||
|
||||
Reference in New Issue
Block a user