No connection needed to look
The schema file is enough to see what Adminium would build. That helps when the database is behind a VPN, or when you want to look before you hand over credentials.
Prisma
An admin panel from your schema.prisma.
Point Adminium at prisma/schema.prisma and it plans the whole admin from that one file, before it has touched a database. Connect the database when you want it to run.
npx @adminiumjs/adminium new my-admin Your names, and the database’s
With @map and @@map, Adminium queries the real column and table names and labels them with the Prisma names your team says out loud.
Relations it can follow
Every @relation becomes a foreign key and a link between records, including the join table of an implicit many-to-many.
What it reads from the file.
Each part of a Prisma schema has a place in the admin.
modeltable@id · @@idprimary key@relationforeign key and a linkenumselect input@map · @@mapthe real column or table name/// commentfield description
Questions
Do I have to use Prisma in my app?
No. Adminium only reads the schema file. It talks to the database itself and does not use the Prisma client.
What about a schema split over several files?
Join them into one file, or import the file that holds your models.
What happens to a field Prisma marks as Unsupported?
It is imported as text, with a warning.
Which other schema formats can it read?
SQL from pg_dump or mysqldump, Drizzle, TypeORM, Sequelize, Rails and Django, as well as a live database.
Your database already has the data. Give it an interface.
Free and open source. Running on your own machine in about a minute.