You can configure the following advanced Deploy client settings in <XLDEPLOY_SERVER_HOME>/centralConfiguration/deploy-client.yaml
.
For more information, see Deploy Properties:
Setting | Description | Default |
---|---|---|
deploy.client.automatically-map-all-deployables | When set to "true", all deployables will be auto-mapped to containers when you set up an initial or update deployment in the GUI, and Deploy will ignore the map.all.deployables.on.initial and map.all.deployables.on.update settings. | true |
deploy.client.automatically-map-all-deployables-on-initial | When set to "true", all deployables will be auto-mapped to containers only when you set up an initial deployment in the GUI. | false |
deploy.client.automatically-map-all-deployables-on-update | When set to "true", all deployables will be auto-mapped to containers only when you set up an update deployment. | false |
deploy.client.session.timeout-minute | Number of minutes before a user's session is locked when the GUI is idle. | 20 |
deploy.client.session-remember-enabled | Show or hide the Keep me logged in option on the log-in screen. | true (option is shown) |
Important: If the client.session.timeout-minute
value is set to 0
(no timeout), and a user session is inactive for more than 30 days, it will be automatically purged from the session database.
Customize Polling Interval
You can customize the default 1s
polling interval behavior with the token gui.task.status.poll-interval-ms
accepting values in ms.
To change the pooling interval value in <XLDEPLOY_SERVER_HOME>/centralConfiguration/deploy-client.yaml
, use as follows:
deploy.client:
gui:
task:
status:
poll-interval-ms: 1000
Replace the ms value with your value for the polling interval. For more information, see deploy.client (deploy-client.yaml).