SQLite databases
A SQLite database is one ordinary file in your account. There's no server process, hostname, port, username, or password: your application opens the file, and that's the whole connection.
That's why SQLite isn't on the Databases page. There's nothing to provision and no credentials to give you; the database already exists wherever your application put it.
The panel still gives you a browser tool for it, in the File Manager next to the file, because the file is the database.
Select the file in the file manager and choose Open in Adminer. Everything else here follows from the database being a file.
Open a database in Adminer
In the File Manager, select one SQLite file. Open in Adminer then appears in two places that do the same thing:
- the context menu (right mouse button)
- the Actions menu in the toolbar
Adminer opens in a new tab, already signed in, showing only that database. You can browse and edit tables, edit and insert rows, run any SQL, import a SQL file, and export a dump.
Adminer runs as your account, with your own permissions, like every other file-manager action. A SQLite file has no credentials of its own; its file permissions already decide who can open it, so a password would protect nothing the filesystem doesn't.
Each database also gets its own Adminer session, so two databases in two tabs stay separate.
How the panel recognizes a database
The panel recognizes a database by its content, not its file name: it reads the start of the file and looks for the SQLite header. So it still offers a database your framework created under an unfamiliar name, and doesn't offer a file that only looks like one.