diff options
author | Matthew Jordan <mjordan@digium.com> | 2014-07-17 21:17:28 +0000 |
---|---|---|
committer | Matthew Jordan <mjordan@digium.com> | 2014-07-17 21:17:28 +0000 |
commit | fc0fecb4768d696db3324bcf6dd03325bb4cd513 (patch) | |
tree | 12615f96e88382b2824d4901f6949571e41ea2e4 /configs/samples/sorcery.conf.sample | |
parent | 1ce23d4534994fdd8bfb8ad3b9ca1884194097be (diff) |
configs: Move sample config files into a subdirectory of configs
This moves all samples configs from configs/ to configs/samples. This allows
for additional sets of sample configuration files to be added in the future.
Review: https://reviewboard.asterisk.org/r/3804/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418870 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'configs/samples/sorcery.conf.sample')
-rw-r--r-- | configs/samples/sorcery.conf.sample | 67 |
1 files changed, 67 insertions, 0 deletions
diff --git a/configs/samples/sorcery.conf.sample b/configs/samples/sorcery.conf.sample new file mode 100644 index 000000000..7406214fb --- /dev/null +++ b/configs/samples/sorcery.conf.sample @@ -0,0 +1,67 @@ +; Sample configuration file for Sorcery Data Access Layer + +; +; Wizards +; +; Wizards are the persistence mechanism for objects. They are loaded as Asterisk modules and register +; themselves with the sorcery core. All implementation specific details of how objects are persisted is isolated +; within wizards. +; + +; +; Caching +; +; A wizard can optionally be marked as an object cache by adding "/cache" to the object type within the mapping. +; If an object is returned from a non-object cache it is immediately given to the cache to be created. Multiple +; object caches can be configured for a single object type. +; + +; +; Object Type Mappings +; +; To allow configuration of where and how an object is persisted object mappings can be defined within this file +; on a per-module basis. The mapping consists of the object type, options, wizard name, and wizard configuration +; data. This has the following format: +; +; object type [/options] = wizard name, wizard configuration data +; +; For example to configure an in-memory wizard for the 'bob' object type: +; +; bob = memory +; +; Or to configure the object type 'joe' from a configuration file: +; +; joe = config,joe.conf +; +; Note that an object type can have multiple mappings defined. Each mapping will be consulted in the order in which +; it appears within the configuration file. This means that if you are configuring a wizard as a cache it should +; appear as the first mapping so the cache is consulted before all other mappings. +; + +; +; The following object mappings are used by the unit test to test certain functionality of sorcery. +; +[test_sorcery_section] +test=memory + +[test_sorcery_cache] +test/cache=test +test=memory + +; +; The following object mapping is the default mapping of external MWI mailbox +; objects to give persistence to the message counts. +; +;[res_mwi_external] +;mailboxes=astdb,mwi_external + +; +; The following object mappings set PJSIP objects to use realtime database mappings from extconfig +; with the table names used when automatically generating configuration from the alembic script. +; +;[res_pjsip] +;endpoint=realtime,ps_endpoints +;auth=realtime,ps_auths +;aor=realtime,ps_aors +;domain_alias=realtime,ps_domain_aliases +;identify=realtime,ps_endpoint_id_ips |