dbxapp provides recurring technical tasks centrally. Developers focus on the business logic of a module and use a shared approach for data, forms, reports, and templates.
Binding building blocks
- dbxDB and DD
- Data access, server connection, table description, permissions, and automatic system fields.
- dbxForm and FD
- Fields, validation, language-dependent messages, saving, and Ajax behavior.
- dbxReport
- Filters, lists, totals, actions, pagination, and exports based on the same definitions.
- dbxTPL
- Reusable presentation without database access or business logic in the template.
Modules instead of special paths
A module encapsulates its business logic, DDs, FDs, and templates. It uses the existing kernel capabilities directly and does not introduce a parallel database, form, template, or security stack.
Mixed database servers
Each DD can be bound to its own server. One installation may combine SQLite and MySQL tables. Module code therefore never accesses a specific database file or PDO connection directly, but always goes through dbxDB and the responsible DD.
Self-hosting and updates
Local configuration and data stay separate from release files. Database changes are carried out via version-based DD migrations and must respect existing server connections.