|
@@ -30,6 +30,9 @@ Create directory or copy appropriate database cluster to `labkeyDocker/postgresq
|
|
|
mkdir -p labkeyDocker/postgresql/data
|
|
|
```
|
|
|
|
|
|
+Links are OK, too. Exact path is set in `bin/env.sh`, see below.
|
|
|
+
|
|
|
+
|
|
|
Check if database runs:
|
|
|
|
|
|
```bash
|
|
@@ -40,14 +43,19 @@ labkeyDocker/bin/stopLabkey.sh
|
|
|
|
|
|
### Files and external modules for LabKey
|
|
|
|
|
|
-If old files and external modules are available, they should be either copied or linked to labkeyDocker/labkeyBase/files and labkeyDocker/labkeyBase/externalModules.
|
|
|
-
|
|
|
+The files and externalModules locations are set in `bin/env.sh`, see `bin/env.sh.sample`:
|
|
|
+```bash
|
|
|
+export EXTERNAL_MODULES=$HOME/externalModules
|
|
|
+export LABKEY_FILES=/data/labkey/files
|
|
|
+```
|
|
|
|
|
|
### Install LabKey binaries
|
|
|
|
|
|
-- run `labkeyDocker/bin/installLabkey.sh 22.3` to unzip the enclosed LabKey binary code and make appropriate links.
|
|
|
+- copy binaries from `https://labkey-public.fmf.uni-lj.si/labkey/Resources to `$HOME/packages`. Remember the version number for next step.
|
|
|
+- run `labkeyDocker/bin/installLabkey.sh 22` to unzip the LabKey binary code and make appropriate links.
|
|
|
- copy `labkeyDocker/bin/env.sh.sample` to `labkeyDocker/bin/env.sh` and set a secret `$PGPASS`, other settings are probably OK,
|
|
|
check `$DOCKERCOMPOSE`
|
|
|
+- copy
|
|
|
- set the same value as `password` in `labkeyDocker/tomcat/conf/Catalina/localhost/labkey.xml`
|
|
|
|
|
|
### Permissions
|