If you want to try it out, the GitCCMS script is available online at GitHub:
The script is useful, only if you have access to a Pressgang CCMS server.
GitCCMS has the following features:
- Supports DocBook 5 and (almost) DocBook 4.
- If the source doc is DocBook 5, it gets converted to DocBook 4 format on the fly and uploaded as DocBook 4 (this is to optimize compatibility with existing content on Pressgang, which is mostly in DocBook 4 format).
- Uploads topics and images.
- Can generate content specs automatically.
- Supports conditional text.
- Supports XML entities.
- Supports olinks (if you create a link between books, the link will be converted to pure text before it is uploaded to Pressgang, so it does not rely on Pressgang to interpret the olinks).
The first thing you need to do is to create a configuration file for GitCCMS in your git repository.
Assuming that you have a repository, MyGitRepo, the first thing you need to do is to create a configuration file for GitCCMS. The configuration file must be called .git-ccms and must be stored in the root directory of the repository, MyGitRepo. Here is an example of a .git-ccms file:
<?xml version="1.0" encoding="UTF-8"?> <context> <books> <book file="BookA/BookA.xml"/> <book file="BookB/BookB.xml"/> </books> <entities file="Library.ent"/> <ignoredirs> <dir name="camel"/> <dir name="amq"/> </ignoredirs> <topicelements> <element tag="simplesect"/> <element tag="section"/> <element tag="info"/> </topicelements> <profiles> <profile name="default"> <project name="Fuse"> <category name="Assigned Writer"> <tag name="johndoe"/> <tag name="janedoe"/> </category> <category name="Product"> <tag name="JBoss Fuse"/> <tag name="JBoss A-MQ"/> </category> <category name="Release"> <tag name="6.1"/> </category> </project> <conditions> <condition match="jbossfuse"/> <condition match="comment"/> </conditions> </profile> </profiles> </context>Note the following points about this GitCCMS configuration:
- The books element is used to list all of the book files in your git repository.
- The entities element specifies a file containing the definitions of all the XML entities appearing in your books.
- The ignoredirs element is useful, if you are using git submodules. The files under the specified directories will not be considered when it comes to creating or updating topics and images (but they are considered for the purpose of compiling tables of cross-references).
- The topicelements element is used to specify which DocBook element types are mapped to topics in the Pressgang CCMS. It is probably best to set this element exactly as shown above. It is not really very flexible at the moment.
- The conditions tag is used to specify the conditions that are enabled when you are using conditional text (this is a standard DocBook feature).
- The project/category/tag elements are used to specify what tags are assigned to newly created topics.
- Some of the configuration settings are specified inside a profile element. In the future, this should allow you to switch configurations easily. But at the moment, only one profile should be used and it must be called default.
Assuming that you have configured GitCCMS as described above, you are now ready to start using GitCCMS. If you have not done so already, you can add the gitccms script to your PATH. For example, on a Linux or UNIX platform:
You can push your DocBook source from the git repository up to the Pressgang server by entering the following command (which must be executed from the top-level directory of your git repository):
By default, this command pushes content to Red Hat's development server (used for testing only). Alternatively, you can specify the Pressgang hostname explicitly using the --host option. If the script completes successfully, you should see that a new hidden file, .git-ccms-commit, is created. This file records the SHA of the last commit that was synchronized with Pressgang. GitCCMS uses this SHA to figure out what changes between synchonizations.
Generating content specs
After uploading your documentation to the Pressgang server, you can generate content specs for all of your books by entering the following command:
You can find the generated specs under the cspec/ directory. You can upload the content specs to Pressgang CCMS using the standard Pressgang csprocessor client (not part of GitCCMS).