This document introduces the concept and development method of Bundle plugin packages. Bundle plugin packages can aggregate multiple plugins together, supporting three types (Marketplace, GitHub, and Package). The document details the entire process of creating a Bundle project, adding different types of dependencies, and packaging the Bundle project.
Marketplace
type. Stores the plugin’s ID and version information. During import, the specific plugin package will be downloaded from the Dify Marketplace.GitHub
type. Stores the GitHub repository address, release version number, and asset filename. During import, Dify will access the corresponding GitHub repository to download the plugin package.Package
type. The plugin package is stored directly within the Bundle. It does not store reference sources, but this might lead to a larger Bundle package size.dify
and copied it to the /usr/local/bin
path, you can run the following command to create a new plugin project:
The name must be 1-128 characters long and can only contain letters, numbers, hyphens, and underscores.
marketplace_pattern
is the reference to the plugin in the marketplace, in the format organization_name/plugin_name:version_number
.
repo_pattern
is the reference to the plugin on GitHub, in the format organization_name/repository_name:release/asset_name
.
package_path
is the directory of the plugin package.
bundle.difybndl
file will be automatically created in the current directory. This file is the final packaged result.