Given that this script is used internally as part of the docker image, it makes sense to ensure it is added to the path directly within the Dockerfile itself, rather than from the docker-compose.yml file. It also needs to be made executable, otherwise the entrypoint command within the docker-compose.yml file will not be able to run it.
If for any reason the name of the database for using misp isn't named "misp", connectivity will fail because database.php does not get updated with the correct name from .env
Ran into this when using a forked version of this project where the web container is run in Docker but MySQL database is running in prod database cluster and required a specific naming convention.
Other parameters in .env are also not updated or translated into database.php
These three are recommended in the latest MISP diagnostics page, so I decided to
add them to the docker build as well.
Signed-off-by: Coleman Kane <ckane@colemankane.org>
The "bionic" distro is older and includes a version of PHP (7.2) that is older than
what MISP recommends (>=7.4). Additionally, "bionic" is supposed to be EOL later this
year, so updating the project to keep current. Necessary changes to PHP & libpoppler
versions.
Signed-off-by: Coleman Kane <ckane@colemankane.org>
The web/run.sh script was using a sed command that had two defects,
preventing the MISP_BASEURL environment from setting the MISP.baseurl
in config.php:
- pattern used '/' as boundaries, making it incompatible with a baseurl
containing that character
- pattern assumed 1 space between 'baseurl' and '=>', but the
config.php has multiple whitespace/tabs, so broadened the pattern to
support any arbitrary length whitespace there
Signed-off-by: Coleman Kane <ckane@colemankane.org>