ktb-jcm d26eaf5dab Update run.sh to include fixing database name in config.php ... 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		2021-10-29 17:06:00 -04:00
..
Dockerfile	fix: remove stix related packages causing install failure, verify with local checksum files instead of remotes.	2021-10-14 10:48:02 +02:00
INSTALL_NODB.sh	fix: remove stix related packages causing install failure, verify with local checksum files instead of remotes.	2021-10-14 10:48:02 +02:00
INSTALL_NODB.sh.sha1	fix: remove stix related packages causing install failure, verify with local checksum files instead of remotes.	2021-10-14 10:48:02 +02:00
INSTALL_NODB.sh.sha256	fix: remove stix related packages causing install failure, verify with local checksum files instead of remotes.	2021-10-14 10:48:02 +02:00
INSTALL_NODB.sh.sha384	fix: remove stix related packages causing install failure, verify with local checksum files instead of remotes.	2021-10-14 10:48:02 +02:00
INSTALL_NODB.sh.sha512	fix: remove stix related packages causing install failure, verify with local checksum files instead of remotes.	2021-10-14 10:48:02 +02:00
healthcheck.patch	Add a healthcheck endpoint: /healthcheck returns status 200, 'ok' payload.	2020-01-28 11:22:06 -08:00
misp-ssl.conf	Copy Apache2 configuration inside container	2021-03-23 10:21:25 +01:00
run.sh	Update run.sh to include fixing database name in config.php	2021-10-29 17:06:00 -04:00