Towards Docker/Korp setup according to CLI argument/envvar.
We're working towards supporting different custom setups of Korp.
These changes make it possible to build one of several custom setups according to a single CLI argument.
Each custom setup has its own custom version of the frontend/app/ directory.
Each of these folders is partly redundant, leading to a lot of added code.
However, they are the correct unit for a single self-contained frontend config of Korp:
Each represents a separate setup of Korp where changes must be made simultaneously to several files,
some of which would break the other setups.
app
app_all
app_lanchart
app_memotest
app_memotest_all
app_test
Another partly redundant addition comes from the CWB encoding scripts in backend/corpora/encodingscripts/.
Some of these are autogenerated.
They could be refactored to a single shell script.
For now, they are not because in each case, a long list of arguments would be required,
which would probably have to be stored in a file anyway.
encode_LANCHARTcorpusAmager.sh
encode_LANCHARTcorpusBornholm.sh
encode_LANCHARTcorpusKoege.sh
encode_MEMO_authcorpora.sh
encode_MEMO_individual_files.sh
encode_MEMO_yearcorpora.sh
encode_MEMOtestcorpus.sh
encode_testcorpus.sh
The script encode.sh is where the corpora to be encoded are selected.
Based on the single CLI argument to docker-compose.
encode.sh
The script create_MEMOconfigs.py is run from the MEMO encoding scripts.
This saves the manual work of creating Korp configs for the MEMO corpora.
create_MEMOconfigs.py
There are changes to both backend and frontend Dockerfiles and start scripts, and to the docker-compose file.
The changes support the CLI argument functionality.
backend/Dockerfile
backend/start.sh
frontend/Dockerfile
frontend/start.sh
docker-compose.yml
An important change consists of setting the CWB registry to a folder on the image rather than the host.
Towards Docker/Korp setup according to CLI argument/envvar.
We're working towards supporting different custom setups of Korp.
These changes make it possible to build one of several custom setups according to a single CLI argument.
Each custom setup has its own custom version of the frontend/app/ directory. Each of these folders is partly redundant, leading to a lot of added code. However, they are the correct unit for a single self-contained frontend config of Korp: Each represents a separate setup of Korp where changes must be made simultaneously to several files, some of which would break the other setups.
Another partly redundant addition comes from the CWB encoding scripts in backend/corpora/encodingscripts/. Some of these are autogenerated. They could be refactored to a single shell script. For now, they are not because in each case, a long list of arguments would be required, which would probably have to be stored in a file anyway.
The script encode.sh is where the corpora to be encoded are selected. Based on the single CLI argument to docker-compose.
The script create_MEMOconfigs.py is run from the MEMO encoding scripts. This saves the manual work of creating Korp configs for the MEMO corpora.
There are changes to both backend and frontend Dockerfiles and start scripts, and to the docker-compose file. The changes support the CLI argument functionality.
An important change consists of setting the CWB registry to a folder on the image rather than the host.
Obsolete files removed: