maintained by ServerContainers
This Dockerfile (available as ghcr.io/servercontainers/phppgadmin) gives you a ready to use phppgadmin installation with optional tls.
Note: This container only supports postgres
database servers.
There is no internal postgres-server available - so you need to setup a seconds container for that (take a look at docker-compose.yml
)
Note: extra_login_security
is false
per default. Make sure you understand what that means in production environments etc.
View in Docker Registry ghcr.io/servercontainers/phppgadmin
View in GitHub ServerContainers/docker-phppgadmin
This Dockerfile is based on the ghcr.io/servercontainers/apache2-ssl-secure debian:bullseye
based image.
You can specify DOCKER_REGISTRY
environment variable (for example my.registry.tld
)
and use the build script to build the main container and it's variants for x86_64, arm64 and arm
You'll find all images tagged like d11.2-a1.18.0-6.1-p1.36.0
which means d<debian version>-a<apache version (with some esacped chars)>-p<phppgadmin version (with some esacped chars)>
.
This way you can pin your installation/configuration to a certian version. or easily roll back if you experience any problems
(don't forget to open a issue in that case ;D).
To build a latest
tag run ./build.sh release
- 2023-03-20
- github action to build container
- implemented ghcr.io as new registry
- moved from
MarvAmBass
toServerContainers
- 2021-08-28
- inital commit
- multiarch build
This container needs to connect to a database, so take a look at the docker-compose.yml
-
DB_HOST
- host of postgres db
- default:
db
-
DB_PORT
- port of postgres db
- default:
5432
-
DEFAULT_DB
- set default db
- default:
template1
-
EXTRA_LOGIN_SECURITY
- since I want this container to be a usable in every situation it's
false
per default - if you want to use this container for a production/long-running environment, you might want to change this
- default:
false
- since I want this container to be a usable in every situation it's
-
DISABLE_TLS
- default: not set - if set yo any value
https
and theHSTS_HEADERS_*
will be disabled
- default: not set - if set yo any value
-
HSTS_HEADERS_ENABLE
- default: not set - if set to any value the HTTP Strict Transport Security will be activated on SSL Channel
-
HSTS_HEADERS_ENABLE_NO_SUBDOMAINS
- default: not set - if set together with HSTS_HEADERS_ENABLE and set to any value the HTTP Strict Transport Security will be deactivated on subdomains