comparison configuration.js @ 26:f2e9365bc8ec

Can use differents backends for node storage. Writing directory-based backend in top of file-based backend.
author Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>
date Mon, 01 Nov 2010 02:39:58 +0100
parents 06abc804e2ab
children bc717575e66a
comparison
equal deleted inserted replaced
25:c774f2ffb271 26:f2e9365bc8ec
23 config.password = 'hellohello'; 23 config.password = 'hellohello';
24 config.superOwner = ['you@example.com']; 24 config.superOwner = ['you@example.com'];
25 config.version = '0.1'; 25 config.version = '0.1';
26 config.os = 'GNU/Linux'; 26 config.os = 'GNU/Linux';
27 config.allowCreateNode = [/@example\.com$/]; // value is an array of RegExp JIDs. If only super-owner should be able to create nodes, use []. 27 config.allowCreateNode = [/@example\.com$/]; // value is an array of RegExp JIDs. If only super-owner should be able to create nodes, use [].
28 28 config.backend = 'directory'; // Put backends in “backends” directory.
29 config.access = 'open'; // values include open, whitelist (by members) and authorize (owners of the node receive notification). presence and roster aren’t implemented yet. 29 config.access = 'open'; // values include open, whitelist (by members) and authorize (owners of the node receive notification). presence and roster aren’t implemented yet.
30 30
31 config.activated = [ 31 config.activated = [
32 'auto-create', 32 'auto-create',
33 //'auto-subscribe', // Impossible à utiliser dans un component 33 //'auto-subscribe', // Impossible à utiliser dans un component