The following issues were addressed. Note that these are edge cases.
* If an empty `/cron-scripts` directory was mounted in the container, an
error would occur.
* If files in the `/cron-scripts` directory had spaces in the name, this
would cause issues.
* stdin was held open when running `docker exec` which would cause hangs
and other issues. The `exec` command is now run non-interactively.
* Custom scripts that failed would interrupt processing of scripts after
it, if any.
It is now possible to override and explicitly specify the shell you
would like used when executing cron tasks. This is accomplished with the
NEXTCLOUD_EXEC_SHELL environment variable, which defaults to bash. You
can also override and customize the arguments provided to that shell
executable via NEXTCLOUD_EXEC_SHELL_ARGS, which defaults to "-c".
See documentation for more detail and examples.
Fixes#6
