Amplication uses plugins to extend the functionality of the generated application. To add more functionality, you can develop your plugins, or can use plugins developed by the community, as they become available.
Available plugins are listed in the Amplication console. Use the UI to install and activate the required plugins. For more information, see documentation
You will soon be able to develop your plugins to implement standards, best practices, and custom integrations, and to do almost anything you want with the generated code.
An GitHub Actions worflow has been added to publish a plugin the npm registry. It lets you specify a pre-determined list of plugin names (additional plugins will have to be added to this list).
latest tag: when using the default branch for this repository when triggering the workflow, the package will be tagged with latest.
beta tag: when using a non-default branch, e.g., a branch for development, when triggering the workflow the package will be tagged with beta.
After publishing the plugin to NPM from the GitHub the plugin will not be visible in the Amplication plugin settings/list immediately. This works in conjunction with the amplication/plugin-catalog, where the plugin-catalog is indexed. Adding the new plugin there will add it to the list of plugins in amplication. Any subsequent version that is released to NPM, will be updated automatically - this can take about 5-10 minutes to propagate.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4