File: matita.conf.xml.in

package info (click to toggle)
matita 0.5.8-2
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 31,144 kB
  • ctags: 10,276
  • sloc: ml: 91,469; xml: 8,768; makefile: 2,021; ansic: 605; sh: 462; php: 381; awk: 121; perl: 36; sql: 11; sed: 4
file content (119 lines) | stat: -rw-r--r-- 4,654 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
<?xml version="1.0" encoding="utf-8"?>
<helm_registry>
  <section name="user">
    <!-- User home directory. Here a ".matita" directory will be created
    and used to store the part of the library developed by the user. -->
    <key name="home">$(HOME)</key>
    <!-- User name. It is used down in this configuration file.  If left
    unspecified, name of the user executing matita will be used (as per
    getent) -->
    <key name="name">$(USER)</key>
  </section>
  <section name="matita">
    <!-- Debug only. Stay away. -->
    <!-- <key name="auto_disambiguation">true</key> -->
    <!-- Debug only. Stay away. -->
    <!-- <key name="environment_trust">true</key> -->
    <key name="basedir">$(user.home)/.matita</key>
    <!-- Where support files are installed -->
    <key name="rt_base_dir">@RT_BASE_DIR@</key>
    <!-- Metadata owner. It will be used to create user-specific tables
    in the SQL database. -->
    <key name="owner">$(user.name)</key>
    <!-- Initial GUI font size. -->
    <!-- <key name="font_size">10</key> -->
    <!--  Perform heavy checks when run interactively (like duplicate check) -->
    <!-- <key name="do_heavy_checks">false</key> -->
  </section>
  <section name="db">
    <!-- 
    Every metadata key must have the following fields:
      1) dbhost: a file:// or a mysql:// path
      2) database name: use extension .db for file:// dbs
      3) username
      4) password: use 'none' for no password
      5) dbtype: one of the following
           'legacy' 
              are read only dbs, used for the Coq/contribs stuff
           'library' 
	      is the standard library, becames writable in publish (-system)
	      mode
           'user' 
              is the user own db (can be the same of marked as ro, tables
              have different names and can coexist)

    Note that:
      exactly one 'user'    db must be specified
      exactly one 'library' db can be specified
      exactly one 'legacy'  db can  be specified
    -->

    <!-- The following snippet is used by the helm team
         note that user's tables are named diffrently from library tables,
	 so they can coexists on the same db -->

    <key name="metadata">@DBHOST@ matita helm none library</key>
    <key name="metadata">@DBHOST@ matita helm none user</key>

    <!-- The following snippet it what you want to use a local sqlite db
         and acess remotely to the coq library trought mowgli
    <key name="metadata">@DBHOST@ matita helm none legacy</key>
    <key name="metadata">file://$(matita.rt_base_dir) metadata.db helm helm library</key>
    <key name="metadata">file://$(matita.basedir) user.db helm helm user</key>
    -->

    <!-- 
    If you have a large amount of metadata, you may be interested in using
    MySql instead of Sqlite. The simplest way to create a MySql database is:
      0) # become an user with database administration privileges
      1) mysqladmin create matita
      2) echo "grant all privileges on matita.* to helm;" | mysql matita
      Note that this way the database will be open to anyone, apply
      stricter permissions if needed.
    -->
  </section>
  <section name="getter">
    <!-- Cache dir for CIC XML documents downloaded from the net.
    Beware that this dir may become really space-consuming. It wont be
    used if all prefexises below are local (i.e. "file:///" URI scheme).
    -->
    <key name="cache_dir">$(user.home)/.matita/getter/cache</key>
    <!-- "Prefixes", i.e.: mappings URI -> URL of the global library
    Each prefix mapps an URI of the cic:/ namespace to an URL where the
    documents can actually be accessed. URL can be in the "file://" or
    "http://" scheme. Only "file://" scheme can be used to store
    documents created by the user.
    Each prefix may be given a list of attributes. Currently supported
    attributes are:
    - "legacy" for parts of the library not generated by Matita (e.g.
      exported from Coq)
    - "ro" for parts of the library which are not writable by the user
      (e.g. the Matita standard library)
    "legacy" implies "ro"
    -->
    <key name="prefix">
      cic:/matita/
      file://$(matita.rt_base_dir)/xml/standard-library/
      ro
    </key>
    <key name="prefix">
      cic:/matita/
      file://$(user.home)/.matita/xml/matita/
    </key>
    <key name="prefix">
      cic:/
      file://@RT_BASE_DIR@/xml/legacy-library/coq/
      legacy
    </key>
    <key name="prefix">
      cic:/
      file:///projects/helm/library/coq_contribs/
      legacy
    </key>
    <key name="prefix">
      cic:/
      http://mowgli.cs.unibo.it/xml/
      legacy
    </key>
  </section>
</helm_registry>