gestioCOF/provisioning
Basile Clement ac1a57d969 Make provisioning script stop immediately on errors
By default, bash will ignore any failing commands and happily proceed to
execute the next ones. This is usually not the behavior the we want in
provisioning script (or ever in scripts, actually): if one step of the
provisioning fails, it doesn't make much sense to proceed with the
following ones.

This simple patch uses `set -e` to ask bash to abort the whole script if
any command within it fails, leading to outputs that are easier to parse
since the commands following a failing one will usually fail also,
hiding the root cause.
2018-02-11 17:01:26 +01:00
..
bootstrap.sh Make provisioning script stop immediately on errors 2018-02-11 17:01:26 +01:00
cron.dev Use the right python interpreter in the cron tasks 2017-08-08 00:19:47 +01:00
cron.md Use the right python interpreter in the cron tasks 2017-08-08 00:19:47 +01:00
daphne.service Switch to nginx + postgres in vagrant 2017-08-09 22:18:26 +01:00
nginx.conf Add SCRIPT_NAME to the production-like server 2017-08-13 14:36:45 +01:00
prepare_django.sh Make provisioning script stop immediately on errors 2018-02-11 17:01:26 +01:00
worker.service Switch to nginx + postgres in vagrant 2017-08-09 22:18:26 +01:00