PI Manager Catalog & Meta-Url

PI Manager uses ocpn-plugins.xml to provide the required metadata and URLs for installation of plugins.

Ocpn-plugins.xml and associated metadata files are located in

Batch files and scripts are available to help create this file ocpn-plugins.xml is created from the individual plugin metadata files located in the data directory.

Please review the Readme file.

In summary

  1. ocpn-plugins.xml is maintained within the project]

    • Users can download updated versions directly from github (=this project [[|]).

  2. Devs can clone this repo and create their own variant which is accessible from the GU using a custom URL.

  3. Devs can issue PR:s against this repo to have their updates incorporated in the main ocpn-plugins-xml.

  4. Dave has access to build the ocpn-plugins.xml in the master branch of the repository.

The scripts require Python

Add Metadata.xml files to the Beta Branch

Once you have build and deployed the 10-12 build environments to your Cloudsmith Repository, you should check the files in the repository and files, and then get the xml’s into the Beta Catalog. For Example: Download each of the recent xml files to a local directory, using the green button at the end and selecting "Save Link".

Then from your local github directory, <code> git clone plugins</code>

You want to clone this. Then checkout the Beta branch.

git checkout -b Beta
git fetch

Then copy your metada files (after looking at some of them for errors) to the metadata directory. Then, reading the README run the python script to join the metadata files into one file call ocpn_plugin.xml Then run the URL check on the file to make sure all urls are good.

Then you can make a PR to the Beta branch to Dave (bdbcat) at OpenCPN/plugins

Create a Meta-url on Alpha Branch

META-URL’s are only accepted on the Branch.

  1. From your local Github repository
    git clone[GitUser]/OpenCPN/plugins.git

  2. Then to go to the Alpha branch.
    git checkout Alpha

  3. From the Alpha branch create your own new corresponding branch which will contain your testing metadata.xml’s.
    git checkout -b [YourName]-alpha

  4. Now go back to the Alpha branch to create your own META-URL xml file.
    git checkout Alpha

  5. Create and add your own Meta-url xml file in
    [GitUser]/plugins/Alpha/metadata alongside the other Plugin Dev xml files.

  6. This file will have a META-URL redirect to your new private branch. Example follows:

  7. In this case the path & file is

  8. The text in the xml file is:

<?xml version="1.0" encoding="UTF-8"?>
<plugin version="1">
  <name> Sean Depagnier Alpha Plugins meta-url </name>
  <version> 1.0 </version>
  <summary> meta-url to Sean's Alpha Plugins by rgleason </summary>
    <meta-url> </meta-url>
  1. Check the new file for format, accuracy and complete tags.

  2. Next run the python tool to build a new ocpn-plugins.xml by executing at the command prompt from the /plugins/ directory
    ''python tools/ocpn-metadata generate –force –userdir metadata –destfile ocpn-plugins.xml ''

  3. See the README. This command collects all the files into one file. You will need to have python configured on your computer.

  4. Then check that Alpha branch has a good ocpn-plugins.xml containing the xml data needed to direct to the cloud sources, including yours and other plugin meta-url redirects.

  5. Now git push your changes to the Alpha branch up to your remote repository, and then push it to 'opencpn/plugins/Alpha'.

  6. Wait for your PR to be accepted.

  7. Your new private branch \`[github user]/plugins branch:[YourName]-alpha`

  8. Now needs to be populated with metadata xmls from your Cloudsmith directory. In my case the branch is
    '' `+ - Copy Cloudsmith metadata xml files for plugins into +` ''

  9. Check those xml for format and complete tags.

  10. Then collect the metadata xmls into a new ocpn-plugins.xml file with
    ''python tools/ocpn-metadata generate –force –userdir metadata –destfile ocpn-plugins.xml ''

  11. Note order of xml data may change, causing it to appear that the PR has more changes than it actually does.

  12. Then push the new files in that branch up to your remote, so that there are some metadata.xml files for your new META-URL in the Alpha branch to link to, so that you can test some plugins in the current Developer’s version of Opencpn.

Also here is another example with squiddio