motor-admin-rails VS Administrate

I think the coolest thing about Rails is actually the great amount of high quality Ruby gems for Rails.

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 should try https://github.com/motor-admin/motor-admin-rails - it builds admin UI with basic CRUD on top of AR models automatically. Unlike other gems where ruby code is required Motor Admin panel can be customized via settings directly in the UI - all configurations are stored in motor.yml file and can be easily transferred between environments.

https://github.com/motor-admin/motor-admin-rails - just adding a link here. u/dpaluy motor admin doesn't require any integration with your rails app js build stack (doesn't depend on webpack/esbuild) - due to that it's very easy to integrate it with any existing app.

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. MOTOR_SYNC_REMOTE_URL=https://remote-app-url/ MOTOR_SYNC_API_KEY=secure-random-string 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...

You should try https://github.com/motor-admin/motor-admin-rails This admin panel gem doesn't use DSL or configuration files and can be customized directly via the UI. More complex things like custom forms and actions can be added via regular rails API controllers.

User roles and permissions via CanCan (learn more).

u/PikachuEXE authorization with row/column level permissions via cancan has been implemented in the newest release - https://github.com/omohokcoj/motor-admin#authorization

thoughtbot/administrate is a well-known framework for administrative screen, but it's not developer friendly。I implement my own template files for Administrate, so when new Administrate version released, It is hard to update Administrate because template file is changed.**

I work at thoughtbot, you might know us for our open source work like administrate, factory_bot or shoulda-matchers.

This looks very similar to Administrate by thoughtbot https://github.com/thoughtbot/administrate

We briefly considered migrating to a full-grown Rails admin interface, such as ActiveAdmin, RailsAdmin, Administrate or Avo. We especially liked Avo which is built on a very modern stack similar to ours (Tailwind + Hotwire + ViewComponents). In the end, we didn’t go this route as we found some of the options a bit too restrictive (even though Avo is very flexible) and we did not feel like trying to amend it to our needs. For example, Avo renders forms in a 1-field-per-row layout while we wanted something more similar to the Tailwind UI Stacked form layout. Nevertheless, we found a great deal of inspiration in the Avo code and its design principles.

We have already covered many use cases for customisation, everything else can be found in the official documentation.

Administrate

I usually tend to create these from Scratch, but moving forward I’ve started to use thoughtbot’s administrate gem. It sticks to the Rails conventions of controllers and routing, so it’s easy to customise and add new functionality to.

That's exactly what we do. Easy to extend trials as needed for users when needed too via https://github.com/thoughtbot/administrate

Documentation https://administrate-demo.herokuapp.com/