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
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>
non-live will make it live again if the container restarts. That seems
better than the default which is that MISP is non-live on container restart.
Ideally live/non-live would be persisted in the database but that's a change
in MISP.
Modification of the file database.php to be able to give the possibility to a MISP to connect to a database with another user.
Addition to download the GPG key on the MISP homepage.