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.

- Add a custom Dockerfile based on the official one with a HEALTCHECK, psql client and static env variables
- Add a custom entrypoint to automatically run the migrations at first launch only and run migration when updating
- Clean separation of networks
- Adding a tag to fix the version of image
- Configure non-secret environment with Docker Compose
- Update database to PG v12