I just checked my changes in PR #22 and I made a mistake in my commit yesterday that makes my code changes in the `entrypoint.sh` unreachable because supervisord is running in foreground mode.
It should be right before the line to start supervisord like in this PR.
Sorry for that.
Run the dmarc report parser script once at startup to avoid PHP errors with a new database.
Also show additional information in the container logs if something failed there.
This should also fix issues #17 and #19
* Update dmarcts-report-parser.conf
Was getting the example error so added env variable so we can use docker-compose.yml to ignore errors. This was experienced with Exchange Online in Microsoft 365. This appears to have resolved the issue and dmarc reports were successfully retrieved and moved into the processed folder.
* Update README.md
* Update README.md
Fixed tab character
* alpine 3.5 to 3.13
* openssl upgrade, remove MimeInfo and SSL perl pkg hacks
* mysql client library upgrades (compatibility with 8)
* image size reduction 703 to 322 MB
* bump upstream sources for viewer and parser
* introduce tags (current and latest docker image 1.0, old image
still available as 0.5)
* Readme: Improve docker-compose sample
- Add attributes "version" and "services" to make it a docker-compose.yml
- Add mariadb service with preconfigured user and database
Resolves https://github.com/gutmensch/docker-dmarc-report/issues/1
* Readme: Describe cron job schedule
It took me a while to figure out why nothing happened after starting the
container. This should help new users to understand that they only have
to wait for the cron job to start.
