|
598 | 598 | "default" : [ |
599 | 599 | ], |
600 | 600 | "deprecatedIn" : null, |
601 | | - "description" : "Log destination(s), e.g. file:///path/to/file (any occurrence of $PID is replaced with the process ID).", |
| 601 | + "description" : "Log destination(s), e.g. file:///path/to/file (any literal occurrence of $PID and @PID@ is replaced with the process ID, and @TEMP_BASE_DIR@ with the path of the current temporary directory).", |
602 | 602 | "dynamic" : false, |
603 | 603 | "enterpriseOnly" : false, |
604 | 604 | "experimental" : false, |
605 | 605 | "hidden" : false, |
606 | 606 | "introducedIn" : null, |
607 | | - "longDescription" : "This option allows you to direct the global or\nper-topic log messages to different outputs. The output definition can be one\nof the following:\n\n- `-` for stdout\n- `+` for stderr\n- `syslog://<syslog-facility>`\n- `syslog://<syslog-facility>/<application-name>`\n- `file://<relative-or-absolute-path>`\n\nTo set up a per-topic output configuration, use\n`--log.output <topic>=<definition>`:\n\n`--log.output queries=file://queries.log`\n\nThe above example logs query-related messages to the file `queries.log`.\n\nYou can specify the option multiple times in order to configure the output\nfor different log topics:\n\n`--log.level queries=trace --log.output queries=file:///queries.log\n--log.level requests=info --log.output requests=file:///requests.log`\n\nThe above example logs all query-related messages to the file `queries.log`\nand HTTP requests with a level of `info` or higher to the file `requests.log`.\n\nAny occurrence of `$PID` in the log output value is replaced at runtime with\nthe actual process ID. This enables logging to process-specific files:\n\n`--log.output 'file://arangod.log.$PID'`\n\nNote that dollar sign may need extra escaping when specified on a\ncommand-line such as Bash.\n\nIf you specify `--log.file-mode <octalvalue>`, then any newly created log\nfile uses `octalvalue` as file mode. Please note that the `umask` value is\napplied as well.\n\nIf you specify `--log.file-group <name>`, then any newly created log file tries\nto use `<name>` as the group name. Note that you have to be a member of that\ngroup. Otherwise, the group ownership is not changed.\n\nThe old `--log.file` option is still available for convenience. It is a\nshortcut for the more general option `--log.output file://filename`.\n\nThe old `--log.requests-file` option is still available. It is a shortcut for\nthe more general option `--log.output requests=file://...`.\n\nTo change the log levels for the specified output you can add a comma separated\nlist of topics with their respective level after the output definition, separated\nby a semicolon:\n`--log.output file:///path/to/file;queries=trace,requests=info`\n`--log.output -;all=error`", |
| 607 | + "longDescription" : "This option allows you to direct the global or\nper-topic log messages to different outputs. The output definition can be one\nof the following:\n\n- `-` for stdout\n- `+` for stderr\n- `syslog://<syslog-facility>`\n- `syslog://<syslog-facility>/<application-name>`\n- `file://<relative-or-absolute-path>`\n\nTo set up a per-topic output configuration, use\n`--log.output <topic>=<definition>`:\n\n`--log.output queries=file://queries.log`\n\nThe above example logs query-related messages to the file `queries.log`.\n\nYou can specify the option multiple times in order to configure the output\nfor different log topics:\n\n`--log.level queries=trace --log.output queries=file:///queries.log\n--log.level requests=info --log.output requests=file:///requests.log`\n\nThe above example logs all query-related messages to the file `queries.log`\nand HTTP requests with a level of `info` or higher to the file `requests.log`.\n\nFor file-based logging, the folders of the destination path need to exist\nalready. They are not created implicitly.\n\nAny occurrence of `$PID` and `@PID` in the log output value is replaced at\nruntime with the actual process ID. This enables logging to process-specific\nfiles:\n\n`--log.output 'file://arangod.log.$PID'`\n\nNote that the dollar sign may need extra escaping when specified on a\ncommand-line such as Bash. You can typically wrap the entire value in single\nquote marks to prevent variable substitution.\n\nAny occurrence of `@TEMP_BASE_DIR@` in the log output value is replaced at\nruntime with the current temporary directory, e.g. `/tmp/arangodb_i37Xxh`\n(automatically created on startup with a randomly generated suffix).\n\nKeep in mind that `@NAME@` is also the syntax for using the value of an\nenvironment variable `NAME`. If there is an environment variable called `PID` or\n`TEMP_BASE_DIR`, then `@PID@` or `@TEMP_BASE_DIR@` is substituted with the\nvalue of the respective environment variable.\n\nIf you specify `--log.file-mode <octalvalue>`, then any newly created log\nfile uses `octalvalue` as file mode. Please note that the `umask` value is\napplied as well.\n\nIf you specify `--log.file-group <name>`, then any newly created log file tries\nto use `<name>` as the group name. Note that you have to be a member of that\ngroup. Otherwise, the group ownership is not changed.\n\nThe old `--log.file` option is still available for convenience. It is a\nshortcut for the more general option `--log.output file://filename`.\n\nThe old `--log.requests-file` option is still available. It is a shortcut for\nthe more general option `--log.output requests=file://...`.\n\nTo change the log levels for the specified output you can add a comma separated\nlist of topics with their respective level after the output definition, separated\nby a semicolon:\n`--log.output file:///path/to/file;queries=trace,requests=info`\n`--log.output -;all=error`", |
608 | 608 | "obsolete" : false, |
609 | 609 | "os" : [ |
610 | 610 | "linux" |
|
1006 | 1006 | }, |
1007 | 1007 | "server.authentication" : { |
1008 | 1008 | "category" : "option", |
1009 | | - "default" : true, |
| 1009 | + "default" : false, |
1010 | 1010 | "deprecatedIn" : null, |
1011 | 1011 | "description" : "Require authentication credentials when connecting (does not affect the server-side authentication settings).", |
1012 | 1012 | "dynamic" : false, |
|
1067 | 1067 | "server.endpoint" : { |
1068 | 1068 | "category" : "option", |
1069 | 1069 | "default" : [ |
1070 | | - "tcp://127.0.0.1:8529" |
| 1070 | + "http+tcp://127.0.0.1:8529" |
1071 | 1071 | ], |
1072 | 1072 | "deprecatedIn" : null, |
1073 | 1073 | "description" : "The endpoint to connect to. Use 'none' to start without a server. Use http+ssl:// as schema to connect to an SSL-secured server endpoint, otherwise http+tcp:// or unix://", |
|
1084 | 1084 | "section" : "server", |
1085 | 1085 | "type" : "string..." |
1086 | 1086 | }, |
| 1087 | + "server.jwt-renewal-threshold" : { |
| 1088 | + "base" : 1, |
| 1089 | + "category" : "option", |
| 1090 | + "default" : 300, |
| 1091 | + "deprecatedIn" : null, |
| 1092 | + "description" : "The time (in seconds) before JWT token expiry to trigger automatic renewal. Default is 300 seconds (5 minutes).", |
| 1093 | + "dynamic" : false, |
| 1094 | + "enterpriseOnly" : false, |
| 1095 | + "experimental" : false, |
| 1096 | + "hidden" : true, |
| 1097 | + "introducedIn" : null, |
| 1098 | + "maxInclusive" : true, |
| 1099 | + "maxValue" : 1.7976931348623157e+308, |
| 1100 | + "minInclusive" : true, |
| 1101 | + "minValue" : 2.2250738585072014e-308, |
| 1102 | + "obsolete" : false, |
| 1103 | + "os" : [ |
| 1104 | + "linux" |
| 1105 | + ], |
| 1106 | + "requiresValue" : true, |
| 1107 | + "section" : "server", |
| 1108 | + "type" : "double" |
| 1109 | + }, |
1087 | 1110 | "server.max-packet-size" : { |
1088 | 1111 | "base" : 1, |
1089 | 1112 | "category" : "option", |
|
1111 | 1134 | "category" : "option", |
1112 | 1135 | "default" : "", |
1113 | 1136 | "deprecatedIn" : null, |
1114 | | - "description" : "The password to use when connecting. If not specified and authentication is required, you are prompted for a password.\nIn startup options, you can wrap the names of environment variables in at signs to use their value, like @ARANGO_PASSWORD@. This helps to expose the password less, like to the process list. Literal @ need to be escaped as @@.", |
| 1137 | + "description" : "The password or access token to use when connecting. If not specified and authentication is required, you are prompted for a password.\nIn startup options, you can wrap the names of environment variables in at signs to use their value, like @ARANGO_PASSWORD@. This helps to expose the password less, like to the process list. Literal @ need to be escaped as @@.", |
1115 | 1138 | "dynamic" : false, |
1116 | 1139 | "enterpriseOnly" : false, |
1117 | 1140 | "experimental" : false, |
|
1152 | 1175 | "category" : "option", |
1153 | 1176 | "default" : "root", |
1154 | 1177 | "deprecatedIn" : null, |
1155 | | - "description" : "The username to use when connecting.", |
| 1178 | + "description" : "The username to use when connecting.\nIf you want to specify an access token as the password, set the user name as encoded in the token.", |
1156 | 1179 | "dynamic" : false, |
1157 | 1180 | "enterpriseOnly" : false, |
1158 | 1181 | "experimental" : false, |
|
0 commit comments