Show HN: Open-source admin panel for Supabase
11–20 of 26 posts
Re: Show HN: Open-source admin panel for Supabase
#12Re: Show HN: Open-source admin panel for Supabase
#13Based on the use cases section, it doesn't seem like this is Supabase specific, but rather postgres specific. Do I have that right? Leveraging Supabase for marketing is a good idea.
Their main home page doesn't mention Supabase: https://www.getmotoradmin.com/
Re: Show HN: Open-source admin panel for Supabase
#14Looks interesting ! I'm currently building a webapp on Supabase and have been considering Retool for admin purposes. What would this offer over something like Retool ? Do you offer specific features tailored to Supabase in order to make the integration easier or do you simply treat it as an ordinary PostgreSQL DB ?
It has several advantages comparing to Retool like simple self-hosting option, CRUD UI out of the box, periodical data reports (aka alerts), unified UI optimized on mobile (instead of retool's more complex UI builder).
Re: Show HN: Open-source admin panel for Supabase
#15Re: Show HN: Open-source admin panel for Supabase
#16Based on the use cases section, it doesn't seem like this is Supabase specific, but rather postgres specific. Do I have that right? Leveraging Supabase for marketing is a good idea.
Re: Show HN: Open-source admin panel for Supabase
#17Re: Show HN: Open-source admin panel for Supabase
#18Wow, this looks really cool. And if it can be used for Supabase I guess it can be used for https://nhost.io too because both are using Postgres?
Re: Show HN: Open-source admin panel for Supabase
#191) It does not appear to have good support for custom Postgres data types (which is reasonable, given that Motor admin appears to work with multiple SQL databases, rather than just Postgres)
2) Its handling of hiding columns is somewhat hacky - if you hide columns from being shown, they're hidden from inserting and editing as well. This can cause issues if you'd like to hide some NOT NULL columns from being displayed.
3) It seems to inject its own 'ID' column into all 'Resources' in the admin panel, and will not be happy if you happen to have an 'ID' column. (As far as I can tell, it seems that the 'Resources' of Motor admin are precisely Ruby on Rails Resources, and that Motor admin generates Rails classes and Resources for you based on your database schema)
4) It does not allow 'unusual' table names such as names containing ':', '--', etc (This seems to cause the generated Ruby class names to become invalid)
To cope with the above issues, I've created Postgres tables for the express purpose of being managed by Motor admin, with the admin tables being sync-ed with the backing tables via triggers. I've attempted to use views instead, but it seems that Motor admin does not recognise views.