You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Any custom setup.xml needs to specify `<bigParentDirectory>/erddapData/</bigParentDirectory>`**
78
+
**If you mount setup.xml file make sure to set`<bigParentDirectory>/erddapData/</bigParentDirectory>`**
79
+
80
+
2. Configure using environmental variables
81
+
82
+
You can set environmental variables to configure ERDDAP's `setup.xml` since version 2.14. See the [ERDDAP documentation](https://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#setupEnvironmentVariables) for details. This can be very useful so you don't need to mount a custom `setup.xml` file into your container. If taking this approach you should look into setting the following ERDDAP config options:
**Depending on your container environment, it may pass in it's own environment variables relating to your resources. Potentially there could be a collision with the `ERDDAP_*` config variables if any of your resources start with ERDDAP.**
75
116
117
+
3. Configure using a shell script
76
118
77
-
2. Mount your own `bigParentDirectory`:
119
+
You can mount a file called `config.sh` to `${CATALINA_HOME}/bin/config.sh` that sets any ERDDAP configuration environmental variables you want to use. This is sourced in the container-provided `setenv.sh` file and and all variables will be exported to be used by ERDDAP for configuration. These will take precedence over environmental variable specified when running the container (see above).
0 commit comments