sorcery.conf 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. ; Sample configuration file for Sorcery Data Access Layer
  2. ;
  3. ; Wizards
  4. ;
  5. ; Wizards are the persistence mechanism for objects. They are loaded as Asterisk modules and register
  6. ; themselves with the sorcery core. All implementation specific details of how objects are persisted is isolated
  7. ; within wizards.
  8. ;
  9. ;
  10. ; Caching
  11. ;
  12. ; A wizard can optionally be marked as an object cache by adding "/cache" to the object type within the mapping.
  13. ; If an object is returned from a non-object cache it is immediately given to the cache to be created. Multiple
  14. ; object caches can be configured for a single object type.
  15. ;
  16. ;
  17. ; Object Type Mappings
  18. ;
  19. ; To allow configuration of where and how an object is persisted object mappings can be defined within this file
  20. ; on a per-module basis. The mapping consists of the object type, options, wizard name, and wizard configuration
  21. ; data. This has the following format:
  22. ;
  23. ; object type [/options] = wizard name, wizard configuration data
  24. ;
  25. ; For example to configure an in-memory wizard for the 'bob' object type:
  26. ;
  27. ; bob = memory
  28. ;
  29. ; Or to configure the object type 'joe' from a configuration file:
  30. ;
  31. ; joe = config,joe.conf
  32. ;
  33. ; Note that an object type can have multiple mappings defined. Each mapping will be consulted in the order in which
  34. ; it appears within the configuration file. This means that if you are configuring a wizard as a cache it should
  35. ; appear as the first mapping so the cache is consulted before all other mappings.
  36. ;
  37. ;
  38. ; The following object mappings are used by the unit test to test certain functionality of sorcery.
  39. ;
  40. [test_sorcery_section]
  41. test=memory
  42. [test_sorcery_cache]
  43. test/cache=test
  44. test=memory
  45. ;
  46. ; The following object mapping is the default mapping of external MWI mailbox
  47. ; objects to give persistence to the message counts.
  48. ;
  49. ;[res_mwi_external]
  50. ;mailboxes=astdb,mwi_external
  51. ;
  52. ; The following object mappings set PJSIP objects to use realtime database mappings from extconfig
  53. ; with the table names used when automatically generating configuration from the alembic script.
  54. ;
  55. ;[res_pjsip]
  56. ;endpoint=realtime,ps_endpoints
  57. ;auth=realtime,ps_auths
  58. ;aor=realtime,ps_aors
  59. ;domain_alias=realtime,ps_domain_aliases
  60. ;identify=realtime,ps_endpoint_id_ips