Improve container image #60
Commits on Jul 25, 2023
-
-
Change: Don't adjust postgres hba config in Dockerfile
The postgres hba config file contains the access rules to the postgres cluster. It will be adjusted in the entry point script in future.
-
Put signal handler into bash function
This allows for easier adjustments in future and for easier quoting.
-
Adjust and improve variables in start-postgresql script for container
Allow for more flexible configuration of the database parameters.
-
Change: Adjust postgres access during container startup
Always allow access via the unix domain socket and allow to configure the authentication for the access via tcp via a POSTGRES_HOST_AUTH_METHOD environment variable. By default users must be authenticated via password when using tcp and the passwords are created using the md5 authentication method.
-
Don't listen on tcp for the initial database setup
We need to initialize the db without influence from the outside. Therefore don't allow access to the database via TCP connections for the moment.
-
Change: Allow access to the postgres db via TCP connections
Listen on all IP addresses of the container when starting the final db cluster. This will allow to access the database via TCP connections from the host for example when exposing the port 5432.
-
Change: Only create postgres db user when it doesn't exist in container
Avoid errors in the log when trying the create the db user twice.
-
Change: Allow to set db user password for container
For TCP access from the outside allow to set a password for the created database user.
-
Change: Only create new postgres db if doesn't exist yet in container
Avoid errors when starting a container with an existing database.
-
Change: Create role and extensions only if they don't exist in container
Avoid errors when starting an already existing and set up database.
