Download the PHP package lagdo/jaxon-dbadmin without Composer

A database admin dashboard based on Jaxon and Adminer

Jaxon DbAdmin is a complete rewrite of Adminer, the popular database admin dashboard.

Jaxon DbAdmin is a Jaxon package, that is inserted into a page of an existing PHP application. So it's also a single page application, and all its operations are performed with Ajax requests.

Separate packages provide ready-to-use applications which run Jaxon DbAdmin respectively with the Laravel, Symfony and Slim frameworks. This blog post on the Jaxon website explains how to install Jaxon DbAdmin on Backpack, a Laravel-based admin panel: https://www.jaxon-php.org/blog/2025/07/install-jaxon-dbadmin-on-backpack.html.

The database access code (and thus the provided features) originates from Adminer. The original code was refactored to take advantage of the latest PHP features (namespaces, interfaces, DI, and so on), and separated into multiple Composer packages.

• https://github.com/lagdo/dbadmin-driver: common classes and interfaces for the database drivers.
• https://github.com/lagdo/dbadmin-driver-pgsql: the database driver for PostgreSQL.
• https://github.com/lagdo/dbadmin-driver-mysql: the database driver for MySQL and MariaDB.
• https://github.com/lagdo/dbadmin-driver-sqlite: the database driver for SQLite.

The https://github.com/lagdo/jaxon-dbadmin package implements the database management features in a Jaxon package. Its UI is built with the https://github.com/lagdo/ui-builder package, which will provide support for multiple frontend frameworks. Bootstrap 5 is the default.

The database packages are developed in this monorepo: https://github.com/lagdo/dbadmin-mono.

Features and current status

This application and the related packages are still being actively developed, and the provided features are still basic and need improvements.

The following features are currently available:

• Browse servers and databases in multiple tabs.
• Open the query editor in multiple tabs, with query text retention.
• Save the current tabs in user preferences.
• Save and show the query history.
• Save queries in user favorites.
• Read database options with an extensible config reader.
• Read database credentials from a secret manager. Currently supported:
  • Infisical
  • AWS Secrets Manager
  • GCP Secret Manager
  • OpenBao (compatible with HashiCorp Vault)
• Show tables and views details.
• Query a table.
• Query a view.
• Execute queries in the query editor.
• Use a better editor for SQL queries.
• Import or export data.
• Insert, modify or delete data in a table.
• Create or drop a database.
• Create or alter a table or view.
• Drop a table or view.

The following features are not yet implemented, and planned for future releases:

• Navigate through related tables.
• Code completion for table and field names in the SQL editor.
• An advanced GUI-based query builder.
• Automated tests.
• Support more secret managers.
  • MS Azure Key Vault
  • Alibaba KMS

The Jaxon DbAdmin application

The https://github.com/lagdo/dbadmin-app repo provides a ready-to-use application, made with the Laravel framework, and Jaxon DbAdmin.

The driver packages for PostgreSQL, MySQL and SQLite are included, so the user just need to add its databases in the config file.

A Docker image is also provided to get started easily. It runs the Laravel based DbAdmin application.

Documentation

Install the Jaxon library so it bootstraps from a config file and handles ajax requests. Here's the documentation.

Install this package with Composer. If a framework extension is available for your framework, you must also install it. It will automate the previous step.

The database drivers

Install the drivers packages for the database servers you need to manage. The following drivers are available:

• PostgreSQL: https://github.com/lagdo/dbadmin-driver-pgsql
• MySQL: https://github.com/lagdo/dbadmin-driver-mysql
• Sqlite: https://github.com/lagdo/dbadmin-driver-sqlite

Declare the package and the database servers in the app.packages section of the Jaxon configuration. See the Jaxon packages documentation.

See the corresponding database driver package for specific database server options.

The CSS and javascript codes

Insert the CSS and javascript codes in the HTML page of your application, as described in the Jaxon documentation.

The UI builder

This package uses the HTML UI builder to build UI components for various frontend frameworks.

The packages for the UI framework in use must also be installed. The following builders are available:

• Bootstrap 5: https://github.com/lagdo/ui-builder-bootstrap5
• Bootstrap 4: https://github.com/lagdo/ui-builder-bootstrap4
• Bootstrap 3: https://github.com/lagdo/ui-builder-bootstrap3

In the above example, the UI will be built with Bootstrap5 components.

Additional config options

There are other config options that can be used to customize the Jaxon DbAdmin operation.

The default option sets a database server Jaxon DbAdmin must connect to when it starts, instead of displaying a blank page.

Access restriction

The access section provides a few options to restrict access to databases on any server.

If the access.server option is set to false at package level, then the access to all servers information will be forbidden, and the user will have access only to database contents. The access.server option can also be set at a server level, and in this case it applies only to that specific server.

In this configuration, the user will get access to server information only on the server with id server_id.

The access.databases and access.schemas options define the set of databases and schemas the user can access. This options can only be defined at server level, and will apply to that specific server. The access.schemas option will apply only on servers which provide that feature.

In this configuration, the user will be able to get access only to three databases on the server with id server_id.

Customizing the package config

The app admin may need to customize the access parameters, depending for example on the connected user account or role.

In this case, the provider option can be used to define a callable that returns the access options as an array, which will then be used to configure the package.

The defined options are passed to the callable, so it can be used as a basis to build the customized config.

Audit logs

The queries executed by the users can be saved in a provided database.

The required options are provided under the queries key.

The queries.database options identify the database where the queries are saved. Depending on the database server, one of the scripts in the migrations/pgsql, migrations/mysql or migrations/sqlite directories in this repository must be used to create the audit database.

The queries.record options indicate which queries are saved. Recording the queries executed in the query builder or the query editor can be enabled or disabled here.

When the queries.admin.history.show and queries.admin.favorite.show options are set to true, the History and Favorites tabs are displayed in the query editor page. When the query history is enabled, the queries.admin.history.distinct option enables the removal of duplicates in the listed queries, while the queries.admin.history.limit option sets the max number of queries for pagination.

The DbAudit package

Jaxon DbAdmin includes a second package which can be use to display the audit logs in another web page. The Lagdo\DbAdmin\App\DbAuditPackage needs to be provided with the audit database connection parameters.

Generally, the access to the audit logs page will be reserved for a selected list of users. While the corresponding options can also be set here, their usage is out of the scope of the package.

The database config readers

Jaxon DbAdmin uses an extensible config reader to read the database credentials. By default, the database credentials are stored in a json, yaml or php config file. Jaxon DbAdmin provides a default config reader which is able to read these values, either from the config file content, or from environment variables.

An alternative config reader can be specified in the package config options. Let say for example the CustomServerConfigProvider class inherits from the default config reader and redefines some functions. The DbAdminPackage and DbAuditPackage can be configured to use it as their config reader.

In addition to the config reader, a custom credential reader can also be provided, and used to read database usernames and passwords from various secret managers.

Jaxon DbAdmin includes a config reader for reading database credentials from an Infisical server. The setup of the required Secrets Management project in the Infisical server is described here: https://www.jaxon-php.org/blog/2026/01/secure-the-jaxon-dbadmin-database-credentials-with-infisical.html.

The Infisical config reader needs to be provided with a closure which returns the key where to find each secret in the server.

The packages can then be configured to use the Infisical config reader.

Data export

Databases can be exported to various types of files: SQL, CSV, and more.

The export feature is configured with two callbacks.

The writer callback saves the export data content in a file. It takes the content and the file name as parameters, and returns the URI to the created file. It must return an empty string in case of error.

The reader callback takes an export file name as parameter, then reads and returns its content. The web app must be configured to call the reader callback and send back the returned content when an HTTP request hits the URI returned by the writer callback.

Both callbacks can use the Jaxon Storage, as in the example below, to read and write the exported files, which can then be saved on different types of filesystems, thanks to the Flysystem library.

The callbacks can also save the file in different locations, depending for example on the application user.

Data import (with file upload)

SQL files can be uploaded and executed on a server. This feature is implemented using the Jaxon ajax upload and Jaxon Storage packages, which then needs to be configured in the Jaxon config file.

In this example, sql_files is the name attribute of the file upload field, and of course /path/to/the/upload/dir needs to be writable. Other parameters can also be defined to limit the size of the uploaded files or retrict their extensions or mime types. the Jaxon ajax upload documentation

Contribute

• Issue Tracker: github.com/lagdo/jaxon-dbadmin/issues
• Source Code: github.com/lagdo/jaxon-dbadmin

License

Jaxon DbAdmin is licensed under the Business Source License 1.1.

The software can be used internally, including in commercial organizations. Providing Jaxon DbAdmin as a hosted, managed, or SaaS service requires a separate commercial license.

After the Change Date specified in the LICENSE file, the applicable version will be available under Apache License 2.0.