Project

General

Profile

Download (2.36 KB) Statistics
| Branch: | Tag: | Revision:
1
##########################################################################
2
# env_file for docker or docker compose 
3
#
4
# see 
5
#    - https://docs.docker.com/compose/compose-file/#env_file
6
# -----------------------------------------------------------------------
7
# The commented ENV variables below show the default values as example!
8
##########################################################################
9

    
10
###
11
# The home directory for the cdm-server process. At this location the cdm-server will 
12
# create the .cdmLibrary folder which will contain per instance configurations,
13
# lucene full text index, and other resources
14
#CDM_HOME=/data
15

    
16
###
17
# The location of the datasources.xml file to be used by the cdm-server. The datasource.xml file 
18
# contains the spring bean definitions of the datasources to be loaded by the server.
19
# NOTE: variable expansion does not work in this file, so the $CDM_HOME can not be used here.
20
#DATASOURCES=/data/.cdmLibrary/datasources.xml
21

    
22
###
23
# The numberof cpu cores available on the host machine, this value is 
24
# being used to configure effective jvm garbage collection
25
#CPU_CORES=1
26

    
27
###
28
# Alternative options for the JVM
29
# You MUST NOT use any of: -Xmx, XX:+UseG1GC -XX:ParallelGCThreads, -XX:ConcGCThreads=, -Duser.home
30
# since these are managed internally in the container. 
31
# To set the heap size:
32
#HEAP_SIZE=1024M
33
# all other options can be set in:
34
#JAVA_OPTIONS=-Dspring.profiles.active=remoting
35

    
36
###
37
# Alternative arguments for the cdm-server.
38
# You may only want to use the following options to avoid conflicts with the once managed in the container:
39
#
40
# -forceSchemaUpdate                      USE THIS OPTION WITH CARE! Outdated cdm database schema versions will 
41
#                                         be forcably updated to the version of the cdm-server. This option is only intended to be
42
#                                         used for development purposes.
43
#
44
# -jmx                                    Start the server with the Jetty MBeans in JMX Management mode.
45
#                                         For testing you can use the following jvm options:
46
#                                         -Dcom.sun.management.jmxremote.ssl=false
47
#                                         -Dcom.sun.management.jmxremote.authenticate=false
48
#                                         -Dcom.sun.management.jmxremote.port=9999
49
#CDMSERVER_ARGS=-forceSchemaUpdate -jmx
(5-5/7)