How vrana/adminer works
Project type and purpose
• Type: Monolithic PHP-based web application, shipped as a single deployable file but organized in modular source form.
• Purpose: Provide a lightweight, extensible database management UI (Adminer) plus a specialized Editor UI for end-user data manipulation.
File structure
• Core code (“adminer/”): All PHP modules under adminer/include (authentication, connection, SQL generation, HTML rendering, plugin host, driver loader). Entry point is adminer/index.php.
• Editor variant (“editor/”): Similar to core but augmented with editor logic, custom UI JS (editor/static/editing.js) and example configuration (editor/example.php). Entry point is editor/index.php.
• Plugins (“plugins/”): PHP plugin scripts and subfolder drivers to extend Adminer. Loaded at runtime by core.
• Designs (“designs/”): CSS themes and metadata. Swappable view layer.
• Drivers (“adminer/drivers” and plugins/drivers): Low-level DB connectors (MySQL, PostgreSQL, SQLite, Mongo, Elastic, etc.).
• Localization (“adminer/lang”): One file per language, plugged in on load.
• Build/Compile (compile.php): Bundles modules into one PHP file.
• External libs (externals/): JS/CSS minifiers and syntax highlighters used at build time.
• Tests (“tests/”): Katalon Recorder suites verifying functionality across databases.
README for additional insights
• Supports multiple SQL and NoSQL engines.
• Single-file deployment is achieved by compile.php using externals.
• Editor is a separate mode for end-users with its own entrypoint.
• Encourages plugin ecosystem for extensibility.
Detail
• How each design folder is pulled in.
• Demonstrate plugin registration flow: Core → Plugin Loader → Plugin Hook → Core.