<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Modules</title><link>https://sourceforge.net/p/codak/home/Modules/</link><description>Recent changes to Modules</description><atom:link href="https://sourceforge.net/p/codak/home/Modules/feed" rel="self"/><language>en</language><lastBuildDate>Thu, 15 Sep 2011 16:17:55 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/codak/home/Modules/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage Modules modified by wauter</title><link>https://sourceforge.net/p/codak/home/Modules/</link><description>CoDAK [Processors] uses [PipeT] modules to transform a document into something else. For example, to transform PDF into text.

CoDAK searches the modules directory for modules that are available. These modules will appear in the processing section of the web interface. A module file ends with .mod and contains at least the URL of the module. For example, the file contents could be:

~~~~~~
url = http://localhost:9009/myModule
~~~~~~

CoDAK is distributed with a number of stock modules, which are installed per default in /etc/pipet/conf.d and accessible via URLs starting with (http://localhost:9009/codak-core). To add a custom module,

1. install the module (see [PipeT])
* check that the module is accessible by calling it from your browser
* add a file to the modules directory with the module's URL
* apply any access restrictions that you may find relevant</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">wauter</dc:creator><pubDate>Thu, 15 Sep 2011 16:17:55 -0000</pubDate><guid>https://sourceforge.netcca15dcbc01d7482b93ab82e96440a8821aad418</guid></item></channel></rss>