From 7a884707ec7189f743dbb8de07e957e2f63e02c8 Mon Sep 17 00:00:00 2001
From: Fabian Affolter <fabian@bernewireless.net>
Date: Tue, 9 Nov 2010 00:43:30 +0100
Subject: Removed

---
 doc/server/plugins/properties.txt | 46 ---------------------------------------
 1 file changed, 46 deletions(-)
 delete mode 100644 doc/server/plugins/properties.txt

diff --git a/doc/server/plugins/properties.txt b/doc/server/plugins/properties.txt
deleted file mode 100644
index fa8bfd884..000000000
--- a/doc/server/plugins/properties.txt
+++ /dev/null
@@ -1,46 +0,0 @@
-.. -*- mode: rst -*-
-
-.. _server-plugins-properties:
-
-==========
-Properties
-==========
-
-The Properties plugin is a connector plugin that adds information from
-properties files into client metadata instances.
-
-Enabling Properties
-===================
-
-First, ``mkdir /var/lib/bcfg2/Properties``. Each property XML file goes
-in this directory. Each will automatically be cached by the server,
-and reread/reparsed upon changes. Add **Properties** to your ``plugins``
-line in ``/etc/bcfg2.conf``.
-
-Data Structures
-===============
-
-Properties adds a new dictionary to client metadata instances that maps
-property file names to PropertyFile instances. PropertyFile instances
-contain parsed XML data as the "data" attribute.
-
-Usage
-=====
-
-Specific property files can be referred to in
-templates as metadata.Properties[<filename>]. The
-data attribute is an LXML element object. (Documented
-`here <http://codespeak.net/lxml/tutorial.html#the-element-class>`_)
-
-Currently, no access methods are defined for this data, but as we
-formulate common use cases, we will add them to the !PropertyFile class
-as methods. This will simplify templates.
-
-Accessing Properties contest from TGenshi
-=========================================
-
-Access contents of ``Properties/auth.xml``
-
-::
-
-    ${metadata.Properties['auth.xml'].data.find('file').find('bcfg2.key').text}
-- 
cgit v1.2.3-1-g7c22