Plugins

BunkerWeb comes with a plugin system making it possible to easily add new features. Once a plugin is installed, you can manage it using additional settings defined by the plugin.

Official plugins

Here is the list of "official" plugins that we maintain (see the bunkerweb-plugins repository for more information) :

Name	Version	Description	Link
ClamAV	1.9	Automatically scans uploaded files with the ClamAV antivirus engine and denies the request when a file is detected as malicious.	bunkerweb-plugins/clamav
Coraza	1.9	Inspect requests using the Coraza WAF (alternative of ModSecurity).	bunkerweb-plugins/coraza
Discord	1.9	Send security notifications to a Discord channel using a Webhook.	bunkerweb-plugins/discord
Slack	1.9	Send security notifications to a Slack channel using a Webhook.	bunkerweb-plugins/slack
VirusTotal	1.9	Automatically scans uploaded files with the VirusTotal API and denies the request when a file is detected as malicious.	bunkerweb-plugins/virustotal
WebHook	1.9	Send security notifications to a custom HTTP endpoint using a Webhook.	bunkerweb-plugins/webhook

How to use a plugin

Automatic

If you want to quickly install external plugins, you can use the EXTERNAL_PLUGIN_URLS setting. It takes a list of URLs separated by spaces, each pointing to a compressed (zip format) archive containing one or more plugins.

You can use the following value if you want to automatically install the official plugins : EXTERNAL_PLUGIN_URLS=https://github.com/bunkerity/bunkerweb-plugins/archive/refs/tags/v1.9.zip

Manual

The first step is to install the plugin by placing its files inside the corresponding plugins data folder. The procedure depends on your integration :

=== "Docker"

When using the [Docker integration](integrations.md#docker), plugins must be placed in the volume mounted on `/data/plugins` in the scheduler container.

The first thing to do is to create the plugins folder :

```shell
mkdir -p ./bw-data/plugins
```

Then, you can drop the plugins of your choice into that folder :

```shell
git clone https://github.com/bunkerity/bunkerweb-plugins && \
cp -rp ./bunkerweb-plugins/* ./bw-data/plugins
```

!!! warning "Using local folder for persistent data"
    The scheduler runs as an **unprivileged user with UID 101 and GID 101** inside the container. The reason behind this is security : in case a vulnerability is exploited, the attacker won't have full root (UID/GID 0) privileges.
    But there is a downside : if you use a **local folder for the persistent data**, you will need to **set the correct permissions** so the unprivileged user can write data to it. Something like that should do the trick :

    ```shell
    mkdir bw-data && \
    chown root:101 bw-data && \
    chmod 770 bw-data
    ```

    Alternatively, if the folder already exists :

    ```shell
    chown -R root:101 bw-data && \
    chmod -R 770 bw-data
    ```

    If you are using [Docker in rootless mode](https://docs.docker.com/engine/security/rootless) or [podman](https://podman.io/), UIDs and GIDs in the container will be mapped to different ones in the host. You will first need to check your initial subuid and subgid :

    ```shell
    grep ^$(whoami): /etc/subuid && \
    grep ^$(whoami): /etc/subgid
    ```

    For example, if you have a value of **100000**, the mapped UID/GID will be **100100** (100000 + 100) :

    ```shell
    mkdir bw-data && \
    sudo chgrp 100100 bw-data && \
    chmod 770 bw-data
    ```

    Or if the folder already exists :

    ```shell
    sudo chgrp -R 100100 bw-data && \
    chmod -R 770 bw-data
    ```

Then you can mount the volume when starting your Docker stack :

```yaml
services:
...
  bw-scheduler:
    image: bunkerity/bunkerweb-scheduler:1.6.2-rc1
    volumes:
      - ./bw-data:/data
...
```

=== "Docker autoconf"

When using the [Docker autoconf integration](integrations.md#docker-autoconf), plugins must be placed in the volume mounted on `/data/plugins` in the scheduler container.


The first thing to do is to create the plugins folder :

```shell
mkdir -p ./bw-data/plugins
```

Then, you can drop the plugins of your choice into that folder :

```shell
git clone https://github.com/bunkerity/bunkerweb-plugins && \
cp -rp ./bunkerweb-plugins/* ./bw-data/plugins
```

Because the scheduler runs as an unprivileged user with UID and GID 101, you will need to edit the permissions :

```shell
chown -R 101:101 ./bw-data
```

Then you can mount the volume when starting your Docker stack :

```yaml
services:
...
  bw-scheduler:
    image: bunkerity/bunkerweb-scheduler:1.6.2-rc1
    volumes:
      - ./bw-data:/data
...
```

=== "Swarm"

!!! warning "Deprecated"
    The Swarm integration is deprecated and will be removed in a future release. Please consider using the [Docker autoconf integration](#__tabbed_1_2) instead.

    **More information can be found in the [Swarm integration documentation](integrations.md#swarm).**

When using the [Swarm integration](integrations.md#swarm), plugins must be placed in the volume mounted on `/data/plugins` in the scheduler container.

!!! info "Swarm volume"
    Configuring a Swarm volume that will persist when the scheduler service is running on different nodes is not covered is in this documentation. We will assume that you have a shared folder mounted on `/shared` across all nodes.

The first thing to do is to create the plugins folder :

```shell
mkdir -p /shared/bw-plugins
```

Then, you can drop the plugins of your choice into that folder :

```shell
git clone https://github.com/bunkerity/bunkerweb-plugins && \
cp -rp ./bunkerweb-plugins/* /shared/bw-plugins
```

Because the scheduler runs as an unprivileged user with UID and GID 101, you will need to edit the permissions :

```shell
chown -R 101:101 /shared/bw-plugins
```

Then you can mount the volume when starting your Swarm stack :

```yaml
services:
...
  bw-scheduler:
    image: bunkerity/bunkerweb-scheduler:1.6.2-rc1
    volumes:
      - /shared/bw-plugins:/data/plugins
...
```

=== "Kubernetes"

When using the [Kubernetes integration](integrations.md#kubernetes), plugins must be placed in the volume mounted on `/data/plugins` in the scheduler container.

The first thing to do is to declare a [PersistentVolumeClaim](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) that will contain our plugins data :

```yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-bunkerweb-plugins
spec:
  accessModes:
    - ReadWriteOnce
resources:
  requests:
    storage: 5Gi
```

You can now add the volume mount and an init container to automatically provision the volume :

```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: bunkerweb-scheduler
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: bunkerweb-scheduler
  template:
    metadata:
      labels:
        app: bunkerweb-scheduler
    spec:
      serviceAccountName: sa-bunkerweb
      containers:
        - name: bunkerweb-scheduler
          image: bunkerity/bunkerweb-scheduler:1.6.2-rc1
          imagePullPolicy: Always
          env:
            - name: KUBERNETES_MODE
              value: "yes"
            - name: "DATABASE_URI"
              value: "mariadb+pymysql://bunkerweb:changeme@svc-bunkerweb-db:3306/db"
          volumeMounts:
            - mountPath: "/data/plugins"
              name: vol-plugins
      initContainers:
        - name: bunkerweb-scheduler-init
          image: alpine/git
          command: ["/bin/sh", "-c"]
          args: ["git clone https://github.com/bunkerity/bunkerweb-plugins /data/plugins && chown -R 101:101 /data/plugins"]
          volumeMounts:
            - mountPath: "/data/plugins"
              name: vol-plugins
      volumes:
        - name: vol-plugins
          persistentVolumeClaim:
            claimName: pvc-bunkerweb-plugins
```

=== "Linux"

When using the [Linux integration](integrations.md#linux), plugins must be written to the `/etc/bunkerweb/plugins` folder :

```shell
git clone https://github.com/bunkerity/bunkerweb-plugins && \
cp -rp ./bunkerweb-plugins/* /etc/bunkerweb/plugins && \
chown -R nginx:nginx /etc/bunkerweb/plugins
```

Writing a plugin

Structure

!!! tip "Existing plugins"

If the documentation is not enough, you can have a look at the existing source code of [official plugins](https://github.com/bunkerity/bunkerweb-plugins) and the [core plugins](https://github.com/bunkerity/bunkerweb/tree/v1.6.2-rc1/src/common/core) (already included in BunkerWeb but they are plugins, technically speaking).

What a plugin structure looks like:

plugin /
    confs / conf_type / conf_name.conf
    ui / actions.py
         hooks.py
         template.html
         blueprints / <blueprint_file(s)>
              templates / <blueprint_template(s)>
    jobs / my-job.py
    templates / my-template.json
          my-template / configs / conf_type / conf_name.conf
    plugin.lua
    plugin.json

conf_name.conf : Add custom NGINX configurations (as Jinja2 templates).
actions.py : Script to execute on the Flask server. This script runs in a Flask context, giving you access to libraries and utilities like jinja2 and requests.
hooks.py : Custom Python file that contains flask's hooks and will be executed when the plugin is loaded.
template.html : Custom plugin page accessed via the UI.
blueprints folder (within ui): This folder is used to override existing Flask blueprints or create new ones. Inside, you can include blueprint files and an optional templates subfolder for blueprint-specific templates.
jobs py file : Custom Python files executed as jobs by the scheduler.
my-template.json : Add custom templates to override the default values of settings and apply custom configurations easily.
plugin.lua : Code executed on NGINX using the NGINX LUA module.
plugin.json : Metadata, settings, and job definitions for your plugin.

Getting started

The first step is to create a folder that will contain the plugin :

mkdir myplugin && \
cd myplugin

Metadata

A file named plugin.json and written at the root of the plugin folder must contain metadata about the plugin. Here is an example :

{
  "id": "myplugin",
  "name": "My Plugin",
  "description": "Just an example plugin.",
  "version": "1.0",
  "stream": "partial",
  "settings": {
    "DUMMY_SETTING": {
      "context": "multisite",
      "default": "1234",
      "help": "Here is the help of the setting.",
      "id": "dummy-id",
      "label": "Dummy setting",
      "regex": "^.*$",
      "type": "text"
    }
  },
  "jobs": [
    {
      "name": "my-job",
      "file": "my-job.py",
      "every": "hour"
    }
  ]
}

Here are the details of the fields :

Field	Mandatory	Type	Description
`id`	yes	string	Internal ID for the plugin : must be unique among other plugins (including "core" ones) and contain only lowercase chars.
`name`	yes	string	Name of your plugin.
`description`	yes	string	Description of your plugin.
`version`	yes	string	Version of your plugin.
`stream`	yes	string	Information about stream support : `no`, `yes` or `partial`.
`settings`	yes	dict	List of the settings of your plugin.
`jobs`	no	list	List of the jobs of your plugin.

Each setting has the following fields (the key is the ID of the settings used in a configuration) :

Field	Mandatory	Type	Description
`context`	yes	string	Context of the setting : `multisite` or `global`.
`default`	yes	string	The default value of the setting.
`help`	yes	string	Help text about the plugin (shown in web UI).
`id`	yes	string	Internal ID used by the web UI for HTML elements.
`label`	yes	string	Label shown by the web UI.
`regex`	yes	string	The regex used to validate the value provided by the user.
`type`	yes	string	The type of the field : `text`, `check`, `select` or `password`.
`multiple`	no	string	Unique ID to group multiple settings with numbers as suffix.
`select`	no	list	List of possible string values when `type` is `select`.

Each job has the following fields :

Field	Mandatory	Type	Description
`name`	yes	string	Name of the job.
`file`	yes	string	Name of the file inside the jobs folder.
`every`	yes	string	Job scheduling frequency : `minute`, `hour`, `day`, `week` or `once` (no frequency, only once before (re)generating the configuration).

Configurations

You can add custom NGINX configurations by adding a folder named confs with content similar to the custom configurations. Each subfolder inside the confs will contain jinja2 templates that will be generated and loaded at the corresponding context (http, server-http, default-server-http, stream, server-stream, modsec, modsec-crs, crs-plugins-before and crs-plugins-after).

Here is an example for a configuration template file inside the confs/server-http folder named example.conf :

location /setting {
	default_type 'text/plain';
    content_by_lua_block {
        ngx.say('{{ DUMMY_SETTING }}')
    }
}

{{ DUMMY_SETTING }} will be replaced by the value of the DUMMY_SETTING chosen by the user of the plugin.

Templates

Check the templates documentation for more information.

LUA

Main script

Under the hood, BunkerWeb is using the NGINX LUA module to execute code within NGINX. Plugins that need to execute code must provide a lua file at the root directory of the plugin folder using the id value of plugin.json as its name. Here is an example named myplugin.lua :

local class     = require "middleclass"
local plugin    = require "bunkerweb.plugin"
local utils     = require "bunkerweb.utils"


local myplugin = class("myplugin", plugin)


function myplugin:initialize(ctx)
    plugin.initialize(self, "myplugin", ctx)
    self.dummy = "dummy"
end

function myplugin:init()
    self.logger:log(ngx.NOTICE, "init called")
    return self:ret(true, "success")
end

function myplugin:set()
    self.logger:log(ngx.NOTICE, "set called")
    return self:ret(true, "success")
end

function myplugin:access()
    self.logger:log(ngx.NOTICE, "access called")
    return self:ret(true, "success")
end

function myplugin:log()
    self.logger:log(ngx.NOTICE, "log called")
    return self:ret(true, "success")
end

function myplugin:log_default()
    self.logger:log(ngx.NOTICE, "log_default called")
    return self:ret(true, "success")
end

function myplugin:preread()
    self.logger:log(ngx.NOTICE, "preread called")
    return self:ret(true, "success")
end

function myplugin:log_stream()
    self.logger:log(ngx.NOTICE, "log_stream called")
    return self:ret(true, "success")
end

return myplugin

The declared functions are automatically called during specific contexts. Here are the details of each function :

Function	Context	Description	Return value
`init`	init_by_lua	Called when NGINX just started or received a reload order. the typical use case is to prepare any data that will be used by your plugin.	`ret`, `msg` `ret` (boolean) : true if no error or else false `msg` (string) : success or error message
`set`	set_by_lua	Called before each request received by the server.The typical use case is for computing before access phase.	`ret`, `msg` `ret` (boolean) : true if no error or else false `msg` (string) : success or error message
`access`	access_by_lua	Called on each request received by the server. The typical use case is to do the security checks here and deny the request if needed.	`ret`, `msg`,`status`,`redirect` `ret` (boolean) : true if no error or else false `msg` (string) : success or error message `status` (number) : interrupt current process and return HTTP status `redirect` (URL) : if set will redirect to given URL
`log`	log_by_lua	Called when a request has finished (and before it gets logged to the access logs). The typical use case is to make stats or compute counters for example.	`ret`, `msg` `ret` (boolean) : true if no error or else false `msg` (string) : success or error message
`log_default`	log_by_lua	Same as `log` but only called on the default server.	`ret`, `msg` `ret` (boolean) : true if no error or else false `msg` (string) : success or error message
`preread`	preread_by_lua	Similar to the `access` function but for stream mode.	`ret`, `msg`,`status` `ret` (boolean) : true if no error or else false `msg` (string) : success or error message `status` (number) : interrupt current process and return status
`log_stream`	log_by_lua	Similar to the `log` function but for stream mode.	`ret`, `msg` `ret` (boolean) : true if no error or else false `msg` (string) : success or error message

Libraries

All directives from NGINX LUA module and are available and NGINX stream LUA module. On top of that, you can use the LUA libraries included within BunkerWeb : see this script for the complete list.

If you need additional libraries, you can put them in the root folder of the plugin and access them by prefixing them with your plugin ID. Here is an example file named mylibrary.lua :

local _M = {}

_M.dummy = function ()
	return "dummy"
end

return _M

And here is how you can use it from the myplugin.lua file :

local mylibrary = require "myplugin.mylibrary"

...

mylibrary.dummy()

...

Helpers

Some helpers modules provide common helpful helpers :

self.variables : allows to access and store plugins' attributes
self.logger : print logs
bunkerweb.utils : various useful functions
bunkerweb.datastore : access the global shared data on one instance (key/value store)
bunkerweb.clusterstore : access a Redis data store shared between BunkerWeb instances (key/value store)

To access the functions, you first need to require the modules :

local utils       = require "bunkerweb.utils"
local datastore   = require "bunkerweb.datastore"
local clustestore = require "bunkerweb.clustertore"

Retrieve a setting value :

local myvar = self.variables["DUMMY_SETTING"]
if not myvar then
    self.logger:log(ngx.ERR, "can't retrieve setting DUMMY_SETTING")
else
    self.logger:log(ngx.NOTICE, "DUMMY_SETTING = " .. value)
end

Store something in the local cache :

local ok, err = self.datastore:set("plugin_myplugin_something", "somevalue")
if not ok then
    self.logger:log(ngx.ERR, "can't save plugin_myplugin_something into datastore : " .. err)
else
    self.logger:log(ngx.NOTICE, "successfully saved plugin_myplugin_something into datastore")
end

Check if an IP address is global :

local ret, err = utils.ip_is_global(ngx.ctx.bw.remote_addr)
if ret == nil then
    self.logger:log(ngx.ERR, "error while checking if IP " .. ngx.ctx.bw.remote_addr .. " is global or not : " .. err)
elseif not ret then
    self.logger:log(ngx.NOTICE, "IP " .. ngx.ctx.bw.remote_addr .. " is not global")
else
    self.logger:log(ngx.NOTICE, "IP " .. ngx.ctx.bw.remote_addr .. " is global")
end

!!! tip "More examples"

If you want to see the full list of available functions, you can have a look at the files present in the [lua directory](https://github.com/bunkerity/bunkerweb/tree/v1.6.2-rc1/src/bw/lua/bunkerweb) of the repository.

Jobs

BunkerWeb uses an internal job scheduler for periodic tasks like renewing certificates with certbot, downloading blacklists, downloading MMDB files, ... You can add tasks of your choice by putting them inside a subfolder named jobs and listing them in the plugin.json metadata file. Don't forget to add the execution permissions for everyone to avoid any problems when a user is cloning and installing your plugin.

Plugin page

Everything related to the web UI is located inside the subfolder ui as we seen in the previous structure section..

Prerequisites

When you want to create a plugin page, you need two files :

template.html that will be accessible with a GET /plugins/<plugin_id>.
actions.py where you can add some scripting and logic with a POST /plugins/<plugin_id>. Notice that this file need a function with the same name as the plugin to work. This file is needed even if the function is empty.

Basic example

!!! info "Jinja 2 template" The template.html file is a Jinja2 template, please refer to the Jinja2 documentation if needed.

We can put aside the actions.py file and start only using the template on a GET situation. The template can access app context and libs, so you can use Jinja, request or flask utils.

For example, you can get the request arguments in your template like this :

<p>request args : {{ request.args.get() }}.</p>

Actions.py

!!! warning "CSRF Token"

Please note that every form submission is protected via a CSRF token, you will need to include the following snippet into your forms :
```html
<input type="hidden" name="csrf_token" value="{{ csrf_token() }}" />
```

You can power-up your plugin page with additional scripting with the actions.py file when sending a POST /plugins/<plugin_id>.

You have two functions by default in actions.py :

pre_render function

This allows you to retrieve data when you GET the template, and to use the data with the pre_render variable available in Jinja to display content more dynamically.

def pre_render(**kwargs)
  return <pre_render_data>

BunkerWeb will send you this type of response :

return jsonify({"status": "ok|ko", "code" : XXX, "data": <pre_render_data>}), 200

<plugin_id> function

This allows you to retrieve data when you make a POST from the template endpoint, which must be used in AJAX.

def myplugin(**kwargs)
  return <plugin_id_data>

BunkerWeb will send you this type of response :

return jsonify({"message": "ok", "data": <plugin_id_data>}), 200

What you can access from action.py

Here are the arguments that are passed and access on action.py functions:

function(app=app, args=request.args.to_dict() or request.json or None)

!!! info "Python libraries" In addition, you can use Python libraries that are already available like : Flask, Flask-Login, Flask-WTF, beautifulsoup4, docker, Jinja2, python-magic and requests. To see the full list, you can have a look at the Web UI requirements.txt. If you need external libraries, you can install them inside the ui folder of your plugin and then use the classical import directive.

Some examples

Retrieve form submitted data

from flask import request

def myplugin(**kwargs) :
	my_form_value = request.form["my_form_input"]
  return my_form_value

Access app config

action.py

from flask import request

def pre_render(**kwargs) :
	config = kwargs['app'].config["CONFIG"].get_config(methods=False)
  return config

template

<!-- metadata + config -->
<div>{{ pre_render }}</div>

Hooks.py

This documentation outlines the lifecycle hooks used for managing different stages of a request within the application. Each hook is associated with a specific phase.

=== "before_request" These hooks are executed before processing an incoming request. They are typically used for pre-processing tasks such as authentication, validation, or logging.

If the hook returns a response object, Flask will skip the request handling and return the response directly. This can be useful for short-circuiting the request processing pipeline.

**Example:**

```python
from flask import request, Response

def before_request():
    print("Before-request: Validating request...", flush=True)
    # Perform authentication, validation, or logging here
    if not is_valid_request(request): # We are in the app context
        return Response("Invalid request!", status=400)

def is_valid_request(request):
    # Dummy validation logic
    return "user" in request
```

=== "after_request" These hooks that run after the request has been processed. They are ideal for post-processing tasks such as cleanup, additional logging, or modifying the response before it is sent back.

They receive the response object as an argument and can modify it before returning it. The first after_request hook to return a response will be used as the final response.

**Example:**

```python
from flask import request

def after_request(response):
    print("After-request: Logging response...", flush=True)
    # Perform logging, cleanup, or response modifications here
    log_response(response)
    return response

def log_response(response):
    # Dummy logging logic
    print("Response logged:", response, flush=True)
```

=== "teardown_request" These hooks are invoked when the request context is being torn down. These hooks are used for releasing resources or handling errors that occurred during the request lifecycle.

**Example:**

```python
def teardown_request(error=None):
    print("Teardown-request: Cleaning up resources...", flush=True)
    # Perform cleanup, release resources, or handle errors here
    if error:
        handle_error(error)
    cleanup_resources()

def handle_error(error):
    # Dummy error handling logic
    print("Error encountered:", error, flush=True)

def cleanup_resources():
    # Dummy resource cleanup logic
    print("Resources have been cleaned up.", flush=True)
```

=== "context_processor" These hooks are used to inject additional context into templates or views. They enrich the runtime context by passing common data (like user information or configuration settings) to the templates.

If a context processor returns a dictionary, the keys and values will be added to the context for all templates. This allows you to share data across multiple views or templates.

**Example:**

```python
def context_processor() -> dict:
    print("Context-processor: Injecting context data...", flush=True)
    # Return a dictionary containing context data for templates/views
    return {
        "current_user": "John Doe",
        "app_version": "1.0.0",
        "feature_flags": {"new_ui": True}
    }
```

This lifecycle hook design provides a modular and systematic approach to managing various aspects of a request's lifecycle:

Modularity: Each hook is responsible for a distinct phase, ensuring that concerns are separated.
Maintainability: Developers can easily add, modify, or remove hook implementations without impacting other parts of the request lifecycle.
Extensibility: The framework is flexible, allowing for additional hooks or enhancements as application requirements evolve.

By clearly defining the responsibilities of each hook and their associated logging prefixes, the system ensures that each stage of request processing is transparent and manageable.

Blueprints

In Flask, blueprints serve as a modular way to organize related components—such as views, templates, and static files—within your application. They allow you to group functionality logically and can be used to create new sections of your app or override existing ones.

Creating a Blueprint

To define a blueprint, you create an instance of the Blueprint class, specifying its name and import path. You then define routes and views associated with this blueprint.

Example: Defining a New Blueprint

from os.path import dirname
from flask import Blueprint, render_template

# Define the blueprint
my_blueprint = Blueprint('my_blueprint', __name__, template_folder=dirname(__file__) + '/templates') # The template_folder is set to avoid conflicts with the original blueprint

# Define a route within the blueprint
@my_blueprint.route('/my_blueprint')
def my_blueprint_page():
    return render_template('my_blueprint.html')

In this example, a blueprint named my_blueprint is created, and a route /my_blueprint is defined within it.

Overriding an Existing Blueprint

Blueprints can also override existing ones to modify or extend functionality. To do this, ensure that the new blueprint has the same name as the one you're overriding and register it after the original.

Example: Overriding an Existing Blueprint

from os.path import dirname
from flask import Flask, Blueprint

# Original blueprint
instances = Blueprint('instances', __name__, template_folder=dirname(__file__) + '/templates') # The template_folder is set to avoid conflicts with the original blueprint

@instances.route('/instances')
def override_instances():
    return "My new instances page"

In this scenario, accessing the URL /instances will display "My new instances page" because the instances blueprint, registered last, overrides the original instances blueprint.

!!! warning "About overriding" Be cautious when overriding existing blueprints, as it can impact the behavior of the application. Ensure that the changes align with the application's requirements and do not introduce unexpected side effects.

All existing routes will be removed from he original blueprint, so you will need to re-implement them if needed.

Naming Conventions

!!! danger "Important" Ensure the blueprint’s name matches the blueprint variable name, else it will not be considered as a valid blueprint and will not be registered.

For consistency and clarity, it's advisable to follow these naming conventions:

Blueprint Names: Use short, all-lowercase names. Underscores can be used for readability, e.g., user_auth.
File Names: Match the filename to the blueprint name, ensuring it's all lowercase with underscores as needed, e.g., user_auth.py.

This practice aligns with Python's module naming conventions and helps maintain a clear project structure.

Example: Blueprint and File Naming

plugin /
    ui / blueprints / user_auth.py
                      templates / user_auth.html

In this structure, user_auth.py contains the user_auth blueprint, and user_auth.html is the associated template, adhering to the recommended naming conventions.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Files

plugins.md

plugins.md

Plugins

Official plugins

How to use a plugin

Automatic

Manual

Writing a plugin

Structure

Getting started

Metadata

Configurations

Templates

LUA

Main script

Libraries

Helpers

Jobs

Plugin page

Prerequisites

Basic example

Actions.py

Hooks.py

Blueprints

Creating a Blueprint

Overriding an Existing Blueprint

Naming Conventions

Files

plugins.md

Latest commit

History

plugins.md

File metadata and controls

Plugins

Official plugins

How to use a plugin

Automatic

Manual

Writing a plugin

Structure

Getting started

Metadata

Configurations

Templates

LUA

Main script

Libraries

Helpers

Jobs

Plugin page

Prerequisites

Basic example

Actions.py

Hooks.py

Blueprints

Creating a Blueprint

Overriding an Existing Blueprint

Naming Conventions