-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathgradle.properties
More file actions
executable file
·99 lines (80 loc) · 2.91 KB
/
gradle.properties
File metadata and controls
executable file
·99 lines (80 loc) · 2.91 KB
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
# These settings are used by the Data Hub Framework when
# communicating with MarkLogic.
# The values in this file are meant as project-wide settings.
# You can override these properties for a specific environment
# by creating a gradle-{environment}.properties file.
# For example, to create a properties file for your prod environment create a file
# named gradle-prod.properties.
#
# ....
mlAppName=unitTest
mlHost=localhost
# Your MarkLogic Username and Password
mlUsername=admin
mlPassword=admin
# If specified, the manage username/password combo is used with the ML Management REST API for managing application
# resources; this user must have the manage-admin and rest-admin roles.
#
# If these are not set, then mlUsername/mlPassword is used for managing application resources.
# mlManageUsername=
# mlManagePassword=
# If specified, the admin username/password combo is used with the ML Management REST API for creating users and roles. This
# user must have the manage-admin or admin role. A good practice is to use your admin account here to create app-specific
# users and roles, which can then be used as mlManageUsername/mlManagePassword and mlUsername/mlPassword.
#
# These properties are also used for connecting to the admin application on port 8001 - e.g. for initializing ML and for
# waiting for ML to restart.
#
# If these properties are not set, then mlUsername/mlPassword will be used.
# mlAdminUsername=
# mlAdminPassword=
# If specified, these values can override where the DHF thinks
# MarkLogic default ports are at. You would only use this if you
# have changed the ports on which MarkLogic listens
#
# mlAppServicesPort=8000
# mlAdminPort=8001
# mlManagePort=8002
mlStagingAppserverName=unitTest-STAGING
mlStagingPort=8010
mlStagingDbName=unitTest-STAGING
mlStagingForestsPerHost=4
mlStagingAuth=digest
mlFinalAppserverName=unitTest-FINAL
mlFinalPort=8011
mlFinalDbName=unitTest-FINAL
mlFinalForestsPerHost=4
mlFinalAuth=digest
mlTraceAppserverName=unitTest-TRACING
mlTracePort=8012
mlTraceDbName=unitTest-TRACING
mlTraceForestsPerHost=1
mlTraceAuth=digest
mlJobAppserverName=unitTest-JOBS
mlJobPort=8013
mlJobDbName=unitTest-JOBS
mlJobForestsPerHost=1
mlJobAuth=digest
mlModulesDbName=unitTest-MODULES
mlModulesForestsPerHost=1
mlTriggersDbName=unitTest-TRIGGERS
mlTriggersForestsPerHost=1
mlSchemasDbName=unitTest-SCHEMAS
mlSchemasForestsPerHost=1
# You can override this to specify an alternate folder for your
# custom forest info. Defaults to user-config/forests/
# mlCustomForestPath=forests
# The name of the Role to create for Hub Access
mlHubUserRole=data-hub-role
mlHubUserName=data-hub-user
mlHubUserPassword=e'IJ%7Ec>yeIEa#/KQ,o
# Users and Roles for unitTest
mlUnitTestUserRole=unittest-role
mlUnitTestUserName=unittest-user
mlUnitTestUserPassword=J$la04#xh13
# Test Database
mlTestRestPort=8010
# Test App Server
mlFinalTestDbName=unitTest-FINAL-TEST
mlFinalTestAppserverName=unitTest-FINAL-TEST
mlFinalTestPort=8014