prisma
Open Source
Not at this point but we might consider it a bit further down the road. What would you see as the biggest benefits (or more generally "reasons") of open sourcing Prisma Studio for your particular case?
In all transparency: The reason why we haven't open sourced Prisma Studio (yet) is because there might be an overlap in the features of Prisma Studio and Prisma Cloud (which will be our commercial product), so we want to keep optionality.
I guess that users have very particular needs with regard to an admin dashboard. Open sourcing would make it possible to customise it to a greater extent.
Just to be clear, is Prisma Studio be a commercial offering or part of the Open Source stack?
Prisma Studio is part of Prisma 2 which is completely free to use and mostly open source. As mentioned above, we're also planning a commercial cloud offering (Prisma Cloud) further down the road.
Well nuts. I came here looking to contribute some UI improvements and debug updating data with multiple primary keys. I guess all I can do is say that being a developer tool, open-sourcing Prisma Studio might attract a lot if improvements from developers who find this tool useful.
What would you see as the biggest benefits (or more generally "reasons") of open sourcing Prisma Studio for your particular case?
I have the same opinion with ragnorc.
My company have been using Prisma since v1, and each time we need an admin dashboard, we would build it from scratch each time.
It might be nice to have a way to start writing Prisma schema and get a working DB and admin site quickly.
Right now, one possible way to do this would be using prisma + nexus + react-admin + ra-data-prisma.
But the developer experience was not great. A lot of boilerplate code was needed to display the data. And react-admin is designed around REST, it doesn't work really well with Prisma data model with nested relations.
Assuming the Prisma Studio code is open sourced, we could generate a customizable version of Prisma Studio, maybe with a config to specify which models to expose etc.
This way, we could get a quick working admin dashboard. Since it just generate the code, we should be able to add new features or hide unnecessary stuffs from the code.
The Prisma Studio feels like it's targeted for developer, while it share some functionality with a common admin dashboard, there's still some differences here and there.
Anyway, Prisma is awesome, thanks for open sourcing it 🎉
@darcien I'm on the same boat. I would checkout https://github.com/keystonejs/keystone. They recently integrated Prisma and give you a customizable backend admin out of the box, with permissions, virtual fields, graphQL playground, etc.
I'm building an Admin UI and some tools that connect to Prisma too and I would love to see how Prisma studio does this and be able to re-use parts of it.
What would you see as the biggest benefits (or more generally "reasons") of open sourcing Prisma Studio for your particular case?
Two ideas I have:
- Performance Improvements (UI can be very slow when displaying a lot of data)
- Visual Improvements (I embed Studio within the local version of my app and manage its child process, would like it to visually match my app)
- Feature Iteration. Prisma Cloud would only benefit from a more feature-rich Prisma Studio. Many other platforms follow this approach: Wordpress, Ghost... They're OSS, but their hosted platforms offer more than just the application itself.
Would also love to see Prisma studio open sourced. Some more usecases:
- being able to modify the output of the paginated content, like adding buttons/actions on each row of some tables (to run specific mutation on that content)
- being able to create custom pages to handle background jobs, cron etc.
The biggest benefit of open sourcing Prisma Studio would be to implement this thing https://github.com/prisma/studio/issues/403
Website states that it is open-source, either open-source it or update the website https://www.prisma.io/docs/concepts/overview/what-is-prisma
Thanks for the feedback on the docs! We updated it, and made it more clear that Studio and Data Browser are not open-source.
Thanks for the feedback on the docs! We updated it, and made it more clear that Studio and Data Browser are not open-source.
Is there a reason this part of Prisma has not been open sourced? :)
Not at this point but we might consider it a bit further down the road. What would you see as the biggest benefits (or more generally "reasons") of open sourcing Prisma Studio for your particular case?
In all transparency: The reason why we haven't open sourced Prisma Studio (yet) is because there might be an overlap in the features of Prisma Studio and Prisma Cloud (which will be our commercial product), so we want to keep optionality.
@mangledbottles here
Not at this point but we might consider it a bit further down the road. What would you see as the biggest benefits (or more generally "reasons") of open sourcing Prisma Studio for your particular case?
In all transparency: The reason why we haven't open sourced Prisma Studio (yet) is because there might be an overlap in the features of Prisma Studio and Prisma Cloud (which will be our commercial product), so we want to keep optionality.
@schickling Perhaps instead of making Prisma Studio open source, you could make it Open core software. That way it doesn't interfere with your cloud offering.
If Prisma studio is not open source is there any way I can contribute to it and If not can I make a chrome extension for prisma studio ?
I wanted to make Prisma studio json viewer and editor for json fields in studio , As it is really annoying to stretch the column or copy (ps: even the ctrl+c doesn't work in that field) and paste it to vs code make changes and pasted it back in studio , Can I do that ?
Prisma Studio should 100% be open source to speed up development if it's gonna stand a chance against other database administration tools like dbeaver. Even phpmyadmin has better ui/ux than prisma studio.
Hey Prisma team, any updates on future plans here? I know there have been considerations in the past to open source Prisma Studio, but I wasn't sure where those were at today.
I use Prisma Studio pretty extensively for data manipulation, but there are a handful of UX quirks that make certain tasks quite a bit more tedious than they would otherwise be.
I'd love to contribute to help improve these things!
We have to migrate off studio because our server crashes every time we try to open prisma model with a lot of related records. Seems like it loads too many of them at once
We have to migrate off studio because our server crashes every time we try to open prisma model with a lot of related records. Seems like it loads too many of them at once
Studio doesn’t scale at all. Dbeaver and datagrip are much better and db agnostic.