See https://stackoverflow.com/a/12142501
Notice : this option can affect consistency of data for MyISAM tables, such as Etherpad store.
But this will avoid a 30 min full lock of the service, and these inconsistencies will be nothing if we really need a backup to restore the database ; we can afford to lose a few revisions and we can also recover a pad content because of the duplications in the table. The consistency is not that important for a pseudo key-value store such as the one that Etherpad uses.

This reverts commit 21c1e819.

This should kill the container if there were errors on one of the 
"children" scripts, making it more obvious that there was a problem.

* replace tabs with spaces
* use a more standard format for 'for' loops

This reverts commit b619ab99.

Vulnerabilities were deleted from wrong folder X)

These vulnerabilities were also fixed by 5b6bd312

Revert this commit to enable backups again.

Backups were run every six hours, but due to the huge increase in the 
size of our DB (Docker volume 'etherpad-db' takes 47 GB at this time), 
backups take almost 3h30 to complete, slowing down the entire instance 
during that period.

...and restore via pg_restore.

Allows to switch a service from a machine to another without having to reconfigure backups. Very useful for migrations for example.