config.template.yaml

#
# Loguru logging level (ERROR, WARNING, INFO, DEBUG, TRACE)
#
log_level: INFO

#
# Present an HTML web UI for browsing and downloading files.
# Disable this to instead expose the ListBuckets API at the root.
#
ui: true

#
# Allow virtual-host-style addressing like 'https://bucketname.yourdomain.org'.
# Path-based addressing is still supported, like 'https://yourdomain.org/bucketname'.
# If this is true, then you need to specify the base URL.
#
virtual_buckets: false

#
# Base URL of your deployment, from the point of view of the client.
#
#base_url: https://yourdomain.org


#--------------------------------------------------------------------------------------
# The list of target storage locations to serve
#--------------------------------------------------------------------------------------
targets:

  #
  # The 'file' client serves data from any local file path
  #
  - name: local_files
    client: file
    options:
      path: .

  #
  # Exposes s3://janelia-cosem-datasets at /cosem-data
  #
  - name: cosem-data
    client: aioboto
    options:
      bucket: janelia-cosem-datasets

  #
  # Exposes s3://janelia-cosem-datasets/aic_desmosome-1 at /cosem-data-with-prefix
  # using the default client (currently aioboto).
  #
  - name: cosem-data-with-prefix
    options:
      bucket: janelia-cosem-datasets
      prefix: aic_desmosome-1

  #
  # Exposes s3://janelia-cosem-datasets at /cosem-data-hidden
  # using the default client (currently aioboto) and makes it unbrowseable
  #
  - name: cosem-data-hidden
    browseable: false
    options:
      bucket: janelia-cosem-datasets

  # To serve data from a private bucket, you must configure an access key and secret key as
  # demonstrated below. This example also shows how to use a custom endpoint.
  #
  #- name: multifish
  #  options:
  #    endpoint: https://s3.us-east-1.lyvecloud.seagate.com/
  #    bucket: multifish
  #    access_key_path: './var/lyve_access_key'
  #    secret_key_path: './var/lyve_secret_key'