|
51 | 51 |
|
52 | 52 | #A version label of the underlying tool and/or this CLAM wrapper
|
53 | 53 | #(If you can derive this dynamically then that is strongly recommended!)
|
54 |
| -SYSTEM_VERSION = "0.3.0" |
| 54 | +SYSTEM_VERSION = "0.3.1" |
55 | 55 |
|
56 | 56 | #The author(s) of the underlying tool and/or this CLAM wrapper
|
57 | 57 | #(If you can derive this dynamically then that is strongly recommended!)
|
|
75 | 75 |
|
76 | 76 | # ======== LOCATION ===========
|
77 | 77 |
|
78 |
| -#Either add a section for your host here, or |
79 |
| -#specify these variables in an external yaml file |
80 |
| -#called $hostname.yaml or config.yaml and use the loadconfig() mechanism. |
81 |
| -#Such an external file will be looked for my default and is the recommended way. |
82 |
| - |
83 |
| -host = os.uname()[1] |
84 |
| -if host == "yourhostname": |
85 |
| - #The root directory for CLAM, all project files, (input & output) and |
86 |
| - #pre-installed corpora will be stored here. Set to an absolute path: |
87 |
| - ROOT = "/tmp/clam.projects/" |
88 |
| - |
89 |
| - #The URL of the system (If you start clam with the built-in webserver, you can override this with -P) |
90 |
| - PORT= 8080 |
91 |
| - |
92 |
| - #The hostname of the system. Will be automatically determined if not set. (If you start clam with the built-in webserver, you can override this with -H) |
93 |
| - #Users *must* make use of this hostname and no other (even if it points to the same IP) for the web application to work. |
94 |
| - HOST = 'yourhostname' |
95 |
| - |
96 |
| - #If the webservice runs in another webserver (e.g. apache, nginx, lighttpd), and it |
97 |
| - #doesn't run at the root of the server, you can specify a URL prefix here: |
98 |
| - #URLPREFIX = "/myservice/" |
99 |
| - |
100 |
| - #Optionally, you can force the full URL CLAM has to use, rather than rely on any autodetected measures: |
101 |
| - #FORCEURL = "http://yourhostname.com" |
102 |
| - |
103 |
| - # ======== AUTHENTICATION & SECURITY =========== |
104 |
| - |
105 |
| - #Users and passwords |
106 |
| - |
107 |
| - #set security realm, a required component for hashing passwords (will default to SYSTEM_ID if not set) |
108 |
| - #REALM = SYSTEM_ID |
109 |
| - |
110 |
| - USERS = None #no user authentication/security (this is not recommended for production environments!) |
111 |
| - #If you want to enable user-based security, you can define a dictionary |
112 |
| - #of users and (hashed) passwords here. The actual authentication will proceed |
113 |
| - #as HTTP Digest Authentication. Although being a convenient shortcut, |
114 |
| - #using pwhash and plaintext password in this code is not secure!! |
115 |
| - |
116 |
| - #USERS = { user1': '4f8dh8337e2a5a83734b','user2': pwhash('username', REALM, 'secret') } |
117 |
| - |
118 |
| - ADMINS = None #List of usernames that are administrator and can access the administrative web-interface (on URL /admin/) |
119 |
| -else: |
120 |
| - #This invokes the automatic loader, do not change it; |
121 |
| - #it will try to find a file named $system_id.$hostname.yml or just $hostname.yml, where $hostname |
122 |
| - #is the auto-detected hostname of this system. Alternatively, it tries a static $system_id.config.yml or just config.yml . |
123 |
| - #You can also set an environment variable CONFIGFILE to specify the exact file to load at run-time. |
124 |
| - #It will look in several paths including the current working directory and the path this settings script is loaded from. |
125 |
| - #Such an external configuration file simply defines variables that will be imported here. If it fails to find |
126 |
| - #a configuration file, an exception will be raised. |
127 |
| - loadconfig(__name__) |
128 |
| - |
129 |
| - |
130 |
| - |
| 78 | +#This invokes the automatic loader, do not change it; |
| 79 | +#it will try to find a file named $system_id.$hostname.yml or just $hostname.yml, where $hostname |
| 80 | +#is the auto-detected hostname of this system. Alternatively, it tries a static $system_id.config.yml or just config.yml . |
| 81 | +#You can also set an environment variable CONFIGFILE to specify the exact file to load at run-time. |
| 82 | +#It will look in several paths including the current working directory and the path this settings script is loaded from. |
| 83 | +#Such an external configuration file simply defines variables that will be imported here. If it fails to find |
| 84 | +#a configuration file, an exception will be raised. |
| 85 | +loadconfig(__name__) |
131 | 86 |
|
132 | 87 |
|
133 | 88 | #Amount of free memory required prior to starting a new process (in MB!), Free Memory + Cached (without swap!). Set to 0 to disable this check (not recommended)
|
|
0 commit comments