/etc/horde/ansel/conf.xml is in php-horde-ansel 3.0.5+debian0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 | <?xml version="1.0"?>
<!-- $Id: a6e80c41dcb0f3f9e6b5a07e76fb2bda605b5263 $ -->
<configuration>
<configtab name="menu" desc="General Settings and Menu">
<configheader>User Interface</configheader>
<configsection name="gallery">
<configinteger name="listlimit" desc="On installations with large
numbers of galleries, it can be useful to disallow using select lists for
gallery selection in blocks. Set this to the maximum number of galleries
that can be displayed in a gallery drop down list. If more than this number
of galleries would appear, then selection list will be disabled."
required="false"/>
<configboolean name="downloadzip" desc="Allow the ability to download an
entire gallery as a .zip file? This is a potential performance hit, and will
likely require a larger memory_limit value.">false</configboolean>
<configboolean name="customlabel" desc="Allow the ability to query the
preference backend for other user's identities? This is a performance hit,
but will allow for displaying something like
"John Smith's Galleries" instead of "jsmith's Galleries".
It also allows a user to specify a custom description to be displayed. So,
for example instead of "John Smith's Galleries", the user could use
"John's Family Photos". This requires a preference backend that
doesn't require an explicit login by the user whose preferences we are
trying to read. If you are getting errors regarding unloadable preferences
when loading Ansel, try turning this off.">true</configboolean>
</configsection>
</configtab>
<configtab name="anselmap" desc="Map Settings">
<configsection name="maps">
<configheader>Maps</configheader>
<configswitch name="driver" desc="Which driver should we use for inline
maps?">
<case name="false" desc="No inline map support" />
<case name="Horde" desc="Horde driver (support for various map providers)">
<configmultienum name="providers" desc="Which layers should we add to the
map?">
<values>
<configspecial application="horde" name="mapsources"/>
</values>
</configmultienum>
<configenum default="false" name="geocoder" desc="Which Geocoder service
should we use?">
<values>
<configspecial application="horde" name="geocoders"/>
</values>
</configenum>
</case>
</configswitch>
</configsection>
</configtab>
<configtab name="vfs" desc="VFS and Photo">
<configheader>VFS Settings</configheader>
<configsection name="images">
<configvfs switchname="type" default="horde"/>
</configsection>
<configsection name="vfs">
<configswitch name="src" desc="How should Horde serve the photo files from
the VFS? If choosing the Sendfile option, you will need a webserver that
supports either the X-Sendfile or the X-LIGHTTPD-send-file headers. If
choosing the VFS-Direct option, be aware that this will bypass
any permissions checking. Anyone that knows or can guess the URL can view
the photo. This option is also only useable with a file based VFS. The PHP
option streams the photo through PHP and is the least efficient, but most
compatible, choice.">
<case name="php" desc="PHP" />
<case name="sendfile" desc="Sendfile"/>
<case name="direct" desc="VFS Direct">
<configstring desc="Specify an alias pointing to the right place on your
filesystem defined in your webserver. Eg. '/ansel-images/'"
name="path"></configstring>
</case>
</configswitch>
</configsection>
<configsection name="image">
<configheader>Photo Generation Settings</configheader>
<configenum name="type" desc="What format should photos be generated in?
Make sure that your server supports whichever format you choose!">
<values>
<value desc="PNG (Highly recommended)">png</value>
<value desc="JPEG">jpeg</value>
</values>
</configenum>
<configstring name="autogen" desc="Should Ansel automatically generate the
screen, thumb, and mini photo views immediately after upload? This will only
work when uploading from Ansel's UI and not when uploading via the api or
mechanisms such as XP Publish. Set this to the maximum number of photos that
may be automatically generated. A value of zero will disable the feature">
0</configstring>
<configboolean name="prettythumbs" desc="Allow the selection of gallery
themes and generation of 'pretty' thumbnails? This can be a performance
hit on some installations but is required for the generation of all but the
most basic image thumbnails." required="false">false</configboolean>
<configboolean name="squaremini" desc="Should Ansel generate square
thumbnails for mini images? Doing so is recommended as this gives a cleaner
look to views. For those that prefer the look of the older mini images that
Ansel generated, uncheck this option">true</configboolean>
<configboolean name="smartcrop" desc="Should Ansel use a SmartCrop algorithm
if available when generating mini or square thumbnails? This gives a better
change that the crop will contain an interesting part of the image, but will
increase CPU usage during image generation."></configboolean>
<configboolean name="tiny" desc="Should Ansel use the TinySrc.mobi webservice
to generate mobile image screen views if appropriate? The gallery must either
be publicly viewable or you must be using the VFS direct option above. If
this is enabled, and these conditions are not met, Ansel will fall back to
an average sized mobile image. Note also that if you are using localhost or
something similar as the server name, this will fail.">false</configboolean>
<configstring name="num_uploads" desc="How many photos should a user be
allowed to upload at once? This setting only applies to the non-javascript
uploader.">5</configstring>
<configstring name="font" required="false" desc="What font would you like
to use when watermarking photos? If you leave this blank, the default for
the particular photo manipulation functions will be used. Make sure you
select a font that is present on your system!"/>
</configsection>
</configtab>
<configtab name="thumbnail" desc="Thumbnail Settings">
<configsection name="thumbnail">
<configheader>Thumbnail Settings</configheader>
<configstring name="perpage" desc="Maximum allowed thumbnails per
page">30</configstring>
<configstring name="width" desc="Thumbnail width">150</configstring>
<configstring name="height" desc="Thumbnail
height">150</configstring>
<configswitch name="unsharp" desc="Should Horde apply an unsharpmask filter
to the image after it's resized?">
<case name="true" desc="Yes">
<configstring name="radius" desc="Radius">0.7</configstring>
<configstring name="amount" desc="Amount">1</configstring>
<configstring name="threshold" desc="Threshold">0.05</configstring>
</case>
<case name="false" desc="No" />
</configswitch>
</configsection>
</configtab>
<configtab name="screen" desc="Screen Photo Settings">
<configsection name="screen">
<configheader>Screen Image Settings</configheader>
<configstring name="width" desc="Screen photo
width">800</configstring>
<configstring name="height" desc="Screen photo
height">600</configstring>
<configswitch name="unsharp" desc="Should Horde apply an unsharpmask filter
to the image after it's resized?">
<case name="true" desc="Yes">
<configstring name="radius" desc="Radius">0.5</configstring>
<configstring name="amount" desc="Amount">1.2</configstring>
<configstring name="threshold" desc="Threshold">0.05</configstring>
</case>
<case name="false" desc="No" />
</configswitch>
</configsection>
</configtab>
<configtab name="ecard" desc="Ecard Settings">
<configsection name="ecard">
<configheader>Ecard Settings</configheader>
<configboolean name="enable" desc="Allow users to send photos as
ecards?">false</configboolean>
</configsection>
</configtab>
<configtab name="comments" desc="Photo Comments">
<configsection name="comments">
<configheader>Photo Comments</configheader>
<configenum name="allow" desc="Can users comment on photos? Note that this
functionality requires the presence of an application that provides the
forums API (such as Agora).">never
<values>
<value desc="Authenticated users">authenticated</value>
<value desc="No one">never</value>
<value desc="All">all</value>
</values>
</configenum>
</configsection>
</configtab>
<configtab name="cache" desc="Cache">
<configsection name="ansel_cache">
<configheader>Cache Settings</configheader>
<configboolean name="usecache" desc="Should we save frequently run queries
and permissions checks in the cache? This will reduce load on your
database server, but could delay the appearance of newly tagged photos
while browsing tags.">false</configboolean>
</configsection>
</configtab>
<configtab name="tags" desc="Tags">
<configsection name="tags">
<configheader>Tag Settings</configheader>
<configboolean name="relatedtags" desc="Allow the display of related tags?
Related tags allow you to easily browse a tag hierarchy, but could be a
performance hit on sites with a large number of similarly tagged photos
since an additional SQL query is performed per related
tag.">false</configboolean>
</configsection>
</configtab>
<configtab name="report_content" desc="Content Reporting">
<configsection name="report_content">
<configheader>Content Reporting Settings</configheader>
<configswitch name="driver" desc="Driver to use">false
<case name="false" desc="Disable">
</case>
<case name="tickets" desc="Create tickets (Whups)">
<configphp name="ticket_params" desc="Enter as a PHP array any
additional arguments for the created ticket (queue, state, priority,
etc). Example for Whups: array('queue' => 2, 'state' => 1, 'priority' => 1,
'type' => 1). You will need to look up the appropriate IDs in Whups's
database, or whatever is appropriate for the ticket system you are
using.">array()</configphp>
<configenum name="allow" desc="Who should be allowed to report
inappropriate content?">all
<values>
<value desc="All users">all</value>
<value desc="Authenticated users">authenticated</value>
<value desc="Never">never</value>
</values>
</configenum>
</case>
<case name="mail" desc="Email">
<configstring name="email" desc="Where should problem report emails be
sent?">webmaster@example.com</configstring>
<configstring name="maildomain" desc="If Horde cannot determine a user's
email address, this domain will be appended to their
username.">example.com</configstring>
<configstring name="username" required="false" desc="If requiring SMTP
authentication without a global SMTP user (in section "Mailer"
and allowing problem reporting for not authenticated users (in section
"Menu Settings"), what username should be use for SMTP
authentication?"/>
<configstring name="password" required="false" desc="The password to use"/>
<configenum name="allow" desc="Who should be allowed to report problems?">all
<values>
<value desc="All users">all</value>
<value desc="Authenticated users">authenticated</value>
<value desc="Never">never</value>
</values>
</configenum>
</case>
<case name="letter" desc="Send internal messages (Letter)">
<configlist name="users" desc="Username to send messages to. If none, ansel admins will be used." />
<configenum name="allow" desc="Who should be allowed to report problems?">all
<values>
<value desc="All users">all</value>
<value desc="Authenticated users">authenticated</value>
<value desc="Never">never</value>
</values>
</configenum>
</case>
</configswitch>
</configsection>
</configtab>
<configtab name="ages" desc="Age">
<configsection name="ages">
<configheader>Age Settings</configheader>
<configlist name="limits" required="false" desc="Age content limitations
(ex 15,18)"/>
<configboolean name="hook" desc="Call hook to get the user
age?">false</configboolean>
</configsection>
</configtab>
<configtab name="faces" desc="Face Detection">
<configsection name="faces">
<configheader>Face Detection</configheader>
<configswitch name="driver">user
<case name="false" desc="Disable" />
<case name="user" desc="Manual selection of faces" />
<case name="facedetect" desc="Face Detect PECL extension">
<configstring name="defs" desc="Path to frontalface XML definition file" >/usr/share/opencv/haarcascades/haarcascade_frontalface_alt.xml</configstring>
</case>
</configswitch>
<configstring name="search" desc="Enable the similar photo functionality for
finding similar faces? Set to 0 to disable, or enter the size, in bytes,
that should be used as the photo's index length. If you don't know what
this is, the default value should be OK for most people. You need the
libpuzzle pecl extension to use this feature." >7</configstring>
</configsection>
</configtab>
</configuration>
|