# Private Plugins {% hint style="info" %} This feature requires an Enterprise license. Please contact to enable the *developer console* on your account. {% endhint %} Private plugins, unlike their public counterpart, are developed, maintained and deployed by Ubidots **users** in order to meet requirements that are not natively addressed by the platform. A private plugin is structured around a specific set of files. These files not only determine the plugin type but also define its logic and overall functionality. The typical file structure for a plugin, regardless of its type, is outlined below: ``` ├── src │ ├── some_files_or_folders ├── LICENSE ├── README.md ├── manifest.toml ``` {% hint style="warning" %} Adhering to this file structure and including all the mentioned files is mandatory for the plugin to be deployed and function correctly. {% endhint %} ## src directory the `src` directory holds the primary components of the plugin. This is where the core logic, main functionalities, and some configuration files are defined. For more specific details about the contents of this directory, please refer to the dedicated section for each type of plugin: {% content-ref url="private-plugins/cron" %} [cron](https://dev.ubidots.com/plugins/private-plugins/cron) {% endcontent-ref %} {% content-ref url="private-plugins/webhook" %} [webhook](https://dev.ubidots.com/plugins/private-plugins/webhook) {% endcontent-ref %} {% content-ref url="private-plugins/widget" %} [widget](https://dev.ubidots.com/plugins/private-plugins/widget) {% endcontent-ref %} {% content-ref url="private-plugins/device" %} [device](https://dev.ubidots.com/plugins/private-plugins/device) {% endcontent-ref %} ## manifest.toml In a broad sense, the manifest file defines the plugin's identity and behavior, that is, it outlines: * Its type * Plugin's current version * Plugin's price * Environmental variables This file contains both shared components that apply to all plugin types and unique components that are specific to each plugin type. The typical manifest file common to all plugins is composed by:

Section	Key	Value	Description	Example
[-]	manifest_version	A valid manifest version. Currently 2.0 is the only one supported.	Manifest version.	`manifest_version = 2.0`
[settings]	version	Any number, according to your versioning system.	Plugin's current version.	`version = "1.1.1"`
[settings]	plugin_type	cron, webhook, device, widget.	Type of plugin	`plugin_type = "widget"`
[settings]	license_name	A valid license name.	The name for your plugin's license.	`license_name = "MIT license"`
[pricing]	price*	A float number.	This is the price that the developer wants to set for the plugin.	`price = 10`
[environment]	Any variable name*	Any value for the variable.	Allows to set environment variables within the plugin.	`UBIDOTS_URL = "https://industrial.api.ubidots.com"`

With that in mind, a manifest file that is common to all plugins, regardless of their type, looks like this: ``` manifest_version = 2.0 [settings] version = "1.1.1" plugin_type = "cron" | "webhook" | "device" | "widget" license_name = "MIT license" [pricing] price = 10 [environment] UBIDOTS_URL = "https://industrial.api.ubidots.com" ``` For detailed information about the specific manifest file components particular to each plugin type, refer to their dedicated pages. {% hint style="info" %} Manifest's file keys marked with a \* are not mandatory. {% endhint %} ## Runtimes ### Python Plugin's Python runtime is based on Python 3.11. You can use it in the `manifest.toml` file as `python3.11`. It contains the following libraries:

Library	Version
requests	2.32.3
pytz	2024.1
msgpack	1.0.8
httpx	0.27.0
aiohttp	3.9.5
lxml	5.2.2
numpy	2.0.0
pandas	2.2.2
python-aqi	0.6.1

### NodeJS Plugin's NodeJS runtime is based on NodeJS 20. You can use it in the `manifest.toml` file as `nodejs:20` It contains the following libraries:

Library	Version
axios	1.5.1

## License The `LICENSE` file provides information about the licensing terms under which the plugin is distributed. Typically, a license file looks like this: ``` Copyright (c) 2021 Ubidots Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE ``` {% hint style="warning" %} This file can't be empty. {% endhint %} ## Readme This is equally important as the `src`directory, since these are the instructions that will guide the users of the plugin. This file must be in Markdown. {% hint style="warning" %} This file can't be empty. {% endhint %}