RailsAdmin is a Rails engine that provides an easy-to-use interface for managing your data.
- Display database tables
- Create new data
- Easily update data
- Safely delete data
- Custom actions
- Automatic form validation
- Search and filtering
- Export data to CSV/JSON/XML
- Authentication (via Devise)
- Authorization (via Cancan)
- User action history (internally or via PaperTrail)
- Supported ORMs
- Mongoid [new]
Gemfile, add the following dependencies:
gem 'fastercsv' # Only required on Ruby 1.8 and below gem 'rails_admin', :git => 'git://github.com/sferik/rails_admin.git'
$ bundle install
And then run:
$ rails g rails_admin:install
This generator will install RailsAdmin and Devise if you
don't already have it installed. Devise is strongly
recommended to protect your data from anonymous users.
It will modify your
mount :: => '/admin', :as => 'rails_admin' # Feel free to change '/admin' to any namespace you need.
It will also add an intializer that will help you getting started. (head for config/initializers/rails_admin.rb)
More on that in the Wiki
Start the server:
$ rails server
You should now be able to administer your site at http://localhost:3000/admin.
All configuration documentation has moved to the wiki: https://github.com/sferik/rails_admin/wiki
Please see list of known issues first.
If you have a question, please check this README, the wiki, and the list of known issues.
If you think you found a bug in RailsAdmin, you can submit an issue. No feature requests or questions please (the mailing list is active and is the preferred venue for feature requests and questions).
In the spirit of free software, everyone is encouraged to help improve this project.
Here are some ways you can contribute:
- by using alpha, beta, and prerelease versions
- by reporting bugs
- by suggesting new features
- by translating to a new language
- by writing or editing documentation
- by writing specifications
- by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
- by refactoring code
- by resolving issues
- by reviewing patches
We use the GitHub issue tracker to track bugs and features. Before submitting a bug report or feature request, please check to make sure it hasn't already been submitted. You can indicate support for an existing issue by voting it up. When submitting a bug report, please include a Gist that includes a stack trace and any details that may be necessary to reproduce the bug, including your gem version, Ruby version, and operating system. Ideally, a bug report should include a pull request with failing specs.
- Fork the project.
- Create a topic branch.
- Implement your feature or bug fix. NOTE - there's a small test app located in the spec/dummy_app directory that you can use to experiment with rails_admin.
- Add documentation for your feature or bug fix.
bundle exec rake doc:yard. If your changes are not 100% documented, go back to step 4.
- Add specs for your feature or bug fix.
bundle exec rake spec. If your changes are not 100% covered, go back to step 6.
- Commit and push your changes.
- Submit a pull request. Please do not include changes to the gemspec, version, or history file. (If you want to create your own version for some reason, please do so in a separate commit.)
This library aims to support and is tested against the following Ruby implementations: