webhippie/postgresql repository overview

⁠postgresql

These are docker images for PostgreSQL⁠ running on our Alpine Linux image⁠.

⁠Versions

For the available versions please look at Docker Hub⁠ or Quay⁠ or check the existing folders within the GitHub repository⁠.

⁠Volumes

• /var/lib/postgresql
• /var/lib/backup
• /etc/postgresql/init.d
• /etc/postgresql/conf.d

⁠Ports

• 5432

⁠Available environment variables

POSTGRESQL_ADDITIONAL_HBA =
POSTGRESQL_ADDITIONAL_IDENT =
POSTGRESQL_AUTH_METHOD = md5
POSTGRESQL_BACKUP_IGNORE = (postgres|template0|template1)
POSTGRESQL_BACKUP_PATH = /var/lib/backup
POSTGRESQL_BACKUP_RETENTION = 14
POSTGRESQL_DATABASE = ${POSTGRESQL_USERNAME}
POSTGRESQL_INITDB_LOCALE = en_US.UTF-8
POSTGRESQL_MAX_CONNECTIONS = 100
POSTGRESQL_PASSWORD = ${POSTGRESQL_ROOT_PASSWORD}
POSTGRESQL_ROOT_PASSWORD =
POSTGRESQL_SKIP_CHMOD = false
POSTGRESQL_SKIP_CHOWN = false
POSTGRESQL_SKIP_MKDIR = false
POSTGRESQL_SUPERUSER_CONNECTIONS = 3
POSTGRESQL_USERNAME =

Extracted by the command: grep -hE ': "\$\{(.*)\}"' latest/overlay/etc/entrypoint.d/*.sh | sed 's/: "\${//' | sed 's/:="/ = /' | sed 's/"}"$//' | sort | uniq

⁠Inherited environment variables

• webhippie/alpine⁠

⁠Contributing

Generally we are following conventional commits⁠ when we apply changes. That way we are able to generate proper changelogs for every release. Please use always pull requests to integrate new functionalities or to fix issues.

For the release process we are following semantic versioning⁠ which clearly indicates if a new version just resolves bugs, includes new features or even includes breaking changes.

After installing the tools via mise install as described above set up the pre-commit hooks so they run automatically on every commit:

prek install --hook-type pre-commit --hook-type commit-msg

If you have changed something on the source you should simply commit following the mentioned conventions:

git checkout -b feat/new-feature
git add --all
git commit -m 'feat: added awesome new feature'
git push --set-upstream origin feat/new-feature

After pushing your changes into the Git repository you should create a pull request on GitHub. If the pull request have been merged and everything built fine it will also create automatically a new release at least once a week.

⁠Authors

• Thomas Boerger⁠

⁠License

MIT

⁠Copyright

Copyright (c) 2015 Thomas Boerger <http://www.webhippie.de>