This repository has been archived by the owner on Apr 16, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
config.php
103 lines (89 loc) · 3.36 KB
/
config.php
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
<?php
$config = array(
/*
* Where is your site located? I will need this information, so please don't lie.
*/
"siteURL" => "http://images.frdnspnzr.de/",
/*
* What's your site called? Basically, that will be the headline.
*/
"siteName" => "Friedensbilder",
/*
* Where are your images? Please name it relative to this file (or absolute)
* and include a trailing /.
*/
"imagePath" => "./images/",
/*
* What file extensions would you like to allow?
* Supported extensions are jpg, jpeg, gif and png.
*/
"allowedExtensions" => array(
"gif",
"jpg",
"jpeg",
"png",
),
/*
* What file extension should use the image loader?
* See "imageLoader" for documentation on what exactly this will do.
* I recommend leaving "gif" here and using a loader that gets rid of the animation.
* Many animated GIFs will decrease site performance drastically. Also, they produce
* much more traffic.
*/
"useImageLoader" => array(
"gif",
),
/*
* What obfuscator should I use?
* Obfuscators are a way of not giving away the filename in the link. Would you
* click a link with "indiana_jones_it_belongs_in_a_museum.jpg" in it? I don't think so,
* because you allready know, what it will show. A link like "89794388901781a35b8810e422d8096d"
* is about 20% cooler, isn't it?
*
* Possibilities are:
* - "NoObfuscation": Images will be linked with their filename. It will look like "spongebob_patrick_eating.gif"
* - "ROT13": Still the filename, but ROT13 encrypted. It will look like "fcbatrobo_cngevpx_rngvat.tvs"
* - "MD5Traverser": Uses MD5 to hash the filename. Slow, but awesome. It will look like "c4e2fe4b39bd2ae5668e90755f5bfd11"
*
* You can use your own Obfuscator if you want to, see developer documentation for this.
*/
"nameObfuscator" => "MD5Traverser",
/*
* What image iterator should I use?
* If you don't know what this is just leave "DefaultFileSystem" and it
* will work pretty much as you'd expect. If you want to dive in a little
* deeper see developer documentation for this.
*/
"imageIterator" => "DefaultFileSystem",
/*
* What image loader should I use?
* Image loaders can convert or manipulate images before showing them in the overview.
* They are, however, not intended to do anything with the images in single image view!
* Also, the loader is only applied to images with the extensions defined in property
* "useImageLoader".
*
* Possibilities are:
* - pngLoader: Will convert images to png. I strongly suggest this one (see "useImageLoader")!
*
* As allways, you can use your own image loader and guess what? See developer documentation for this!
*/
"imageLoader" => "pngLoader",
/*
* The following attributes are only used if you would like to allow GifStream access (See gifstream.in)
* If you just set "allowGifStream" to false everything else will not be relevant
*/
"allowGifStream" => false,
/*
* License for your GifStream pictures. This is a string, so use wisely!
*/
"gifStreamLicense" => null,
/*
* Unique Identifier for your GifStream. Philipp suggests UTI, I don't mind, as long as it's
* globally unique. If you really can't think of one I'll just use your sites name, but that
* doesn't sound very unique and you're going to hell for it. You have been warned.
*
* Mine, for example, is "de.frdnspnzr.friedensbilder.gifstream"
*/
"gifStreamIdentifier" => null,
)
?>