We provide access to development servers, which run developer extensions which allow you to use the Plugin Tool to develop your plugin. We don’t provide developer access to live systems to ensure stability.
We’ll set up a development application for you. This can either be a blank system, or a copy of another application.
Developing a plugin
Please get in touch if you need anything. We’re happy to answer questions on specific APIs, or the best way of achieving something. Your questions help us improve this documentation and develop the Platform.
Naming a plugin
To avoid the names of plugins clashing with each other, we’ll give you a prefix for all your plugin names, based on your organisation name. For example, the Acme Corporation may be asked to prefix all their plugin names with “
acme_”, for example,
We review all plugins before they’re installed on the live servers. This gives us an opportunity to spot any problems before they occur, as well as being an integral part of our approach to security.
--minimise option to test the minimised version of the plugin.
It’s also a good idea to run the
check command to perform final checks before going live.
You should be developing your plugin using a source control system, and provide us access so we can take a copy of each version you’d like to deploy. We provide free Fossil Hosting, but are happy to work with other source control systems if you host the repository.
You can develop more than one plugin in a repository. Plugins should be in a directory, named after that plugin, at the root of the repository.
When you request we deploy a plugin, we’ll take the latest version of the plugin from the
trunk branch (or equivalent for your source control system), review it, then copy it to the live servers.
Installation on live applications
If you’re updating an existing plugin, all applications which use it on the live systems will automatically be updated with the latest version.
For new plugins, you’ll need to install it.