-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using active_admin in my current app #8
Comments
Nice work! Did you design as well? It's great that active admin handles non enlish characters nicely out of On Sat, Sep 8, 2012 at 12:58 AM, Agis Anastasopoulos <
|
Thank you. No I didn't design this one, it's a paid theme. Yes that's great about activeadmin.. and the DSL it provides for customizing the views is very nice (formtastic is great). The things to notice about my activeadmin implementation is that:
|
ahh i never did try to create a new resource so didnt get to see the editors. Actually i tried deploying active_admin to heroku as well and it was a pain to figure out. ActiveAdmin has a wiki regarding it and I followed all the steps and got it working. They did forget to explicity include one of activeadmins stylesheets in the assets precompile hook but apart from that it worked. I love heroku but sometimes issues like these sometimes want to push me back to rolling rails on my own server. |
It doesn't have any editors, it's just a plain text field. Yes activeadmin requires some configuration to work with the Cedar stack. You have to add some of its assets to the precompilation list in application.rb (not production.rb because Heroku doesn't look at it at all). |
Hey guys. I'm currently developing a blog-like app which can be found here: https://github.com/Agis-/bathliving and live here: http://bathliving.herokuapp.com
I'm using active_admin and you can see how I implemented it live here: http://bathliving.herokuapp.com/admin (user: [email protected], password: password).
If you have any questions, comments, suggestions go ahead, let me know!
The text was updated successfully, but these errors were encountered: