petems
Motor Admin gem has been developed to replace the outdated ActiveAdmin/RailsAdmin/Blazer gems in your existing or future Rails app.
Unlike other Rails admin gems, Motor Admin doesn't use DSL or any other type of customization/configuration Ruby APIs.
All adjustments in Motor Admin can be made directly in the UI via WYSIWYG interfaces.
This probably makes it the first no-code/low-code Rails open-source admin engine.
Would appreciate any feedback regarding the gem!
Show HN: Webhooks development relay with VS Code extension
>Auto-generating the GUI from SQL schema, similar to the original Django Admin
Thats exactly how Motor Admin works :)
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).
Show HN: Open-source admin panel for Supabase
For instance, you can bootstrap a powerful Admin panel for your Rails project in no time with https://github.com/motor-admin/motor-admin-rails gem.
You can learn about how to upgrade to the latest version here:
https://github.com/motor-admin/motor-admin/releases/tag/late...
For instance, you can deploy an admin panel with https://www.getmotoradmin.com/ (plug) and save a lot of time on building custom internal tools.
You can try it in docker instead - also it's possible to deploy it on heroku for free.
All configurations are stored in motor.yml file which is automatically generated in root directory.
There might be two ways handling configurations: 1. Use git to create commits with new configurations in motor.yml and deploy/pull that git repo on the production host in order to update the configs.
2. rake motor:sync to sync configurations directly to production app host via API.
There a bit of info about configurations sync between environment here:
https://github.com/motor-admin/motor-admin-rails#configurati...
So let's say to want to add user to some LDAP directory once the user is created in Motor Admin.
In order to do that you need to override the default user creation form and send data from that form to your API back end so you can handle user creation in LDAP from there: https://monosnap.com/file/3CD1qKgNoTBOhwTwzLiNJXTUNgi8yH
All those API requests are sent with JWT header - so it's possible to validate them on the back end.
My concern is that with REST backend it would become a much complex tool and will make it harder to build an admin panel - Retool does a good job building internal tools with visual builders and connecting APIs - but that definitively takes more time to build admin panel with it than with Motor Admin.
The example you mentioned can be easily implemented in Motor Admin via SQL queries or admin UI configurations with direct connection to the database and the performance would be probably better than it could have been with Graphsql.
It's hard to say how difficult it could be but some companies already migrated from activeadmin to motor admin gem for their rails projects and they claim that it was worth it :)
With Motor Admin you don't need to - you can achieve almost everything AppSmith/Retool does with simpler configurations using the unified motor admin UI.
You can try it yourself locally on macOS, Ubuntu or in docker if you're on windows: