File: Plugin-Guidelines.md

package info (click to toggle)
cacti 1.2.30%2Bds1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 67,176 kB
  • sloc: php: 123,193; javascript: 29,825; sql: 2,595; xml: 1,823; sh: 1,228; perl: 194; makefile: 65; python: 51; ruby: 9
file content (26 lines) | stat: -rw-r--r-- 789 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
# Plugin Guidelines

## Overview

This section will help the Cacti plugin developer structure their plugins.
However, the best way to create a plugin is to borrow someone elses.  There
are Cacti plugin examples on [Cactis GitHub page](https://github.com/Cacti) and
you can find them all over GitHub just by searching.

## Plugin Creation

Use the following guidelines for creating your first plugin.

## Plugin Namespaces

All plugins must use namespace isolation either through Classes, or using
the plugin name in their functions.  This prevents name space collisions.

An example plugin is provided here [Example Plugin](resources/example.tgz).

## Publishing Your Plugin

GitHub is the best place to publish your plugins.  Learn to use it.

---
Copyright (c) 2004-2024 The Cacti Group