/**
       * This lock is used to ensure safe and correct cancellation, it ensures that a new task is
       * not scheduled while a cancel is ongoing. Also it protects the currentFuture variable to
       * ensure that it is assigned atomically with being scheduled.
       */
      private final ReentrantLock lock = new ReentrantLock();

      /** The future that represents the next execution of this task. */

labels.failure_url_error_log=Log
labels.failure_url_web_config_name=Web Crawl Config
labels.failure_url_file_config_name=File Crawl Config
labels.system_info_configuration=System Info
labels.system_info_env_title=Environment Variable Properties
labels.system_info_prop_title=System Properties
labels.system_info_fess_prop_title=App Properties
labels.system_info_bug_report_title=Bug Report Properties

	// check for omitted fields
	zb0001Len := uint32(5)
	var zb0001Mask uint8 /* 5 bits */
	_ = zb0001Mask
	if z.OldDataDir == "" {
		zb0001Len--
		zb0001Mask |= 0x10
	}
	// variable map header, size zb0001Len
	err = en.Append(0x80 | uint8(zb0001Len))
	if err != nil {
		return
	}

	// skip if no fields are to be emitted
	if zb0001Len != 0 {
		// write "BaseOptions"

```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. ### Configure TLS To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates. While...

```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. ### Configure TLS To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates. While...

```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. ### Configure TLS To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates. While...

    // ============================================================

    /** Fess thumbnail path configuration key. */
    public static final String FESS_THUMBNAIL_PATH = "fess.thumbnail.path";

    /** Fess variable path configuration key. */
    public static final String FESS_VAR_PATH = "fess.var.path";

    /** Fess log level configuration key. */
    public static final String FESS_LOG_LEVEL = "fess.log.level";

```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. ### Configure TLS To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates. While...

```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates....

The URL and port *must* be accessible by the client for the redirection to work. For deployments behind a load balancer, proxy, or ingress rule where the MinIO host IP address or port is not public, use the `MINIO_BROWSER_REDIRECT_URL` environment variable to specify the external hostname for the redirect. The LB/Proxy must have rules for directing traffic to the Console port specifically. For example, consider a MinIO deployment behind a proxy `https://minio.example.net`, `https://console.minio.example.net`...