-
Notifications
You must be signed in to change notification settings - Fork 1
/
application.conf
56 lines (43 loc) · 1.68 KB
/
application.conf
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
curacao {
boot-package = "com.kolich.havalo"
async-context-timeout = 60s
thread-pool {
name-format = "havalo-%d"
size = 256
}
}
## ===================================================
## Havalo-kvs application configuration.
## ===================================================
havalo-kvs {
repository {
# The repository root: where all repositories known to this Havalo
# instance live on disk. In production deployments this should be
# overridden to point at something a bit more real world, ideally
# would point at some NFS directory or other root on disk outside
# of the web-application's WEB-INF directory.
base = "WEB-INF/work"
# The max filename length of any object on disk.
# For example, if this is set to 2, then the file path's to repositories
# and objects on disk will look something like "FG/71/61/==/34/...".
# Note you shouldn't need to change this unless you're running Havalo
# on a system with special needs.
maxfilename.length = 2
}
# Defalt admin user UUID and API access secret.
api {
# The UUID of the Admin user/repository.
# NOTE: You should change this in production deployments.
admin.uuid = "00000000-0000-0000-0000-000000000000"
# The corresponding secret of the Admin user/repository.
# NOTE: You should change this in production deployments.
admin.secret = "overrideme"
}
upload {
# Max upload default in bytes (defaults to 2GB).
# This is essentially the maximum size of any object in the
# K,V store -- API consumers will not be allowed to 'PUT' any
# objects greater than this size.
max.size = 2147483648
}
}