Service type
Adminer service
Web-based database administration service for managing linked MariaDB, MySQL, and PostgreSQL databases inside a stack.
Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.
On Wodby
How Adminer runs on Wodby
Link and login
- The required
dblink points to one database service. It setsADMINER_DEFAULT_DB_DRIVER,ADMINER_DEFAULT_DB_HOST(host and port) andADMINER_DEFAULT_DB_NAME. - The image uses them to prefill the login form: the system, the server and the database. The user name and the password are not prefilled and are not stored in the container; they are typed in by the person logging in.
- The interface listens on port
80.
Configuration
Changed through environment variables on the service:
ADMINER_PLUGINS: space-separated plugin names,tables-filter edit-textareaby default. A name that the Adminer version does not ship stops the container at start.ADMINER_DESIGN: a bundled theme.PHP_UPLOAD_MAX_FILESIZE,PHP_POST_MAX_SIZE,PHP_MEMORY_LIMIT,PHP_MAX_EXECUTION_TIME: limits for uploading and running SQL files.
The service has no volume: nothing it holds is persistent.
Basic auth
Wodby protects this service's public domains with basic auth by default: each app service of it gets its own generated password, which members reveal on the environment's Endpoints > Auths page. Services inside the environment reach it directly, without the password. The protection can be switched off when the app is created, or later by deleting the entry; a stack can also turn the default off.
Overview
Technical profile and packaging
Versions
Source repository
Public Helm chart
Ports and protocols
Labels
Stacks
Use it inside ready-made stacks or your own
Runtime wiring
Reuse connectivity, storage, and runtime defaults
Endpoints
Technical domains
Service links
These links define which other services can connect to Adminer when it is used inside a stack.
db
Eligible linked services