3

We've been using rails_admin for a project for a year. It's good, but it would be preferable to have an admin interface that ran in a totally separate process from the main Rails app and from a completely independent code base. rails_admin has so many dependencies that upgrading it along with the main Rails app has proven brittle.

So the functionality we would need is just basic crud for the database tables, with a little bit of magic to make editing associations easier.

Are there any light-weight solutions out there for this? Bonus points for being lightweight & Sinatra-based rather than Rails-based.

dan
  • 43,914
  • 47
  • 153
  • 254
  • How would this gem (or else) would know about your models, validations etc? – Robin Aug 29 '12 at 22:44
  • Maybe I could symlink the app/models directory – dan Aug 29 '12 at 23:21
  • In a related question, I try to solve the issue of sharing models etc. http://stackoverflow.com/questions/18133645/how-to-keep-dry-with-a-activeadmin-or-railsadmin-separate-from-the-main-applica/18136464?noredirect=1#18136464 – berkes Aug 09 '13 at 07:03

1 Answers1

1

I would look into git submodules or subversion externals. The way I've done something similar to this is to

  1. List item migrate the models into a standalone ruby project.
  2. put them in a 'core' subdirectory/module.
  3. Create a new rails project just for administration.
  4. Share the models between the 2 rails apps using an svn external of the 'core' directory into each project's app/models directory.
oberfreak
  • 1,799
  • 13
  • 20
LanceW
  • 71
  • 1
  • 1