forked from cross-solution/YAWIK
-
Notifications
You must be signed in to change notification settings - Fork 0
/
build.properties.dist
53 lines (40 loc) · 1.33 KB
/
build.properties.dist
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
; This file contains configuration options. By executing:
;
; ./phing.phar generate-autoload-config
;
; The values are written to configuration files located in config/autoload
;
email=
;
; role of the initial user.
; possible roles: [ user | recruiter |admin ]
;
role=recruiter
;
; external appKey. You can add jobs and users by using a simple API. This
; external.appkey is a pre-shared key, which allows your external application
; to authenticate. An empty value disables this feature.
;
external.app.key=will-be-overwritten-during-build-process
external.app.prefix=myapp
; subject of the initial email, if somebody logs into via a social network
mail.first_login.subject=Welcome to the YAWIK demo
auth.suffix=
;
; Email development system settings
; (module/Core/config/core.mails.development.php.dist).
;
; Override recipient for every mail send. (including CC and BCC)
; Use comma to separate multiple addresses.
;
mail.develop.override_recipient=
;
; For Developers: If you plan to contribute to the development, you can define some deployment variables.
;
; where to deploy the api docs generated via phpdoc
deploy.ssh.host =
deploy.ssh.user =
deploy.docs.target =
; als long there is no mechanism to read properties files from modules, we
; put this config option here
yawik.demoskin.piwik=/../../module/YawikDemoSkin/view/.piwik.phtml