rPath Appliance Platform:Package a Plugin

From rPath Wiki

To make an rPath Appliance Platform plugin available for appliance development after development, package the plugin for Conary to install the plugin directories to /usr/lib/raa. By default, the rPath Appliance Platform checks this directory at startup for plugins.

The directory structure should resemble the following:

• /usr/lib/raa
  • <project_name>
    • <plugin_name>
      • srv
      • web
        • static

These should reflect the directories created in the development environment. The paths to the srv and web directories for SamplePlugin in project example would be:

/usr/lib/raa/example/SamplePlugin/srv
/usr/lib/raa/example/SamplePlugin/web

The <project_name> convention is used only as the top-level namespace for organizing plugins originating from the same source.

Test before packaging

Copy the plugin directory to /usr/lib/raa on the local system or a test system to test functions prior to packaging.

Test after packaging

After packaging, install the package on the local system or test system and test its functions again.

There must be a custom configuration that enables the plugin for the appliance, and this is typically packaged and controlled separately from the plugin. See rPath Appliance Platform Agent:Configuration for more information.

ADD SAMPLE PACKAGE RECIPE HERE

Troubleshooting the Package

Content needed...