omero-blitz.properties

##
## omero-blitz.properties
## ----------------------
##
## DO NOT EDIT!
##
## This properties file is compiled into omero-blitz.jar and serves as a default
## for all server-side values (client configuration happens differently).
##
## Any of these properties can be altered by using :program:`omero config`. MODIFYING
## THIS FILE DOES NOT ALTER SERVER BEHAVIOR. It solely defines the defaults
## at compile time!
##
## For an overview of these properties, see
## https://docs.openmicroscopy.org/latest/omero/sysadmins/config.html
##
## Properties marked with "DEVELOPMENT" should not be used in production.

#############################################
## FS properties
#############################################

# Template for FS managed repository paths.
# Allowable elements are:
#
# ::
#
#    %user%         bob
#    %userId%       4
#    %group%        bobLab
#    %groupId%      3
#    %year%         2011
#    %month%        01
#    %monthname%    January
#    %day%          01
#    %time%         15-13-54.014
#    %institution%  University of Dundee
#    %hash%         0D2D8DB7
#    %increment%    14
#    %subdirs%      023/613
#    %session%      c3fdd5d8-831a-40ff-80f2-0ba5baef448a
#    %sessionId%    592
#    %perms%        rw----
#    %thread%       Blitz-0-Ice.ThreadPool.Server-3
#    /              path separator
#    //             end of root-owned directories
#
# These are described further at :doc:`fs-upload-configuration`
#
# The path must be unique per fileset to prevent upload conflicts,
# which is why %time% includes milliseconds.
#
# A // may be used as a path separator: the directories preceding
# it are created with root ownership, the remainder are the user's.
# At least one user-owned directory must be included in the path.
#
# The template path is created below :property:`omero.managed.dir`,
# e.g. :file:`/OMERO/ManagedRepository/${omero.fs.repo.path}/`
omero.fs.repo.path=%user%_%userId%//%year%-%month%/%day%/%time%

# Rules to apply to judge the acceptability of FS paths for writing into
# :property:`omero.managed.dir`, being any comma-separated non-empty subset of:
#
# - Windows required
# - Windows optional
# - UNIX required
# - UNIX optional
# - local required
# - local optional
#
# Minimally, the "required" appropriate for the server is recommended.
# Also applying "optional" rules may make sysadmin tasks easier,
# but may be more burdensome for users who name their files oddly.
# "local" means "Windows" or "UNIX" depending on the local platform,
# the latter being applied for Linux and Mac OS X.
omero.fs.repo.path_rules=Windows required, UNIX required

# Checksum algorithms supported by the server for new file uploads,
# being any comma-separated non-empty subset of:
#
# - Adler-32
# - CRC-32
# - MD5-128
# - Murmur3-32
# - Murmur3-128
# - SHA1-160
# - File-Size-64
#
# In negotiation with clients, this list is interpreted as being in
# descending order of preference.
omero.checksum.supported=SHA1-160, MD5-128, Murmur3-128, Murmur3-32, CRC-32, Adler-32, File-Size-64

#############################################
## grid configuration
##
## For more information, see
##
## https://docs.openmicroscopy.org/latest/omero/sysadmins/grid.html
#############################################

# registry_timeout is the milliseconds which
# the registry and other services will wait
# on remote services to respond.
omero.grid.registry_timeout=5000