search

anjlab / anjlab-widgets

UI Widgets on top of anjlab-bootstrap-rails
MIT License
54 stars 15 forks source link

uninitialized constant Anjlab #11

Closed DevanB closed 11 years ago

DevanB commented 11 years ago

When I am deploying to my server and it runs the migrate command I receive this error:

uninitialized constant Anjlab /home/deployer/apps/eventsappdev.us/releases/20130820183312/config/initializers/simple_form.rb:52:in `block in <top (required)>'

here is my simple_form initializer: https://gist.github.com/DevanB/6285398

DevanB commented 11 years ago

Possibly no relation - when I updated the anjlab-bootstrap-rails gem, I still get this uninitialized constant Anjlab error

yury commented 11 years ago

Can you gist your gemfile?

DevanB commented 11 years ago

https://gist.github.com/DevanB/6303627

I assume I have something in the wrong order. I'm fairly new to Rails, so I'm learning still. Thanks for all the help Yury!

yury commented 11 years ago

Ok, :assets group doesn't work in production. So you should move everything out.

DevanB commented 11 years ago

Oh really? I'm not on Rails 4. I'm on Rails 3.2.13. Does this still apply?

If so, should I move all gems out of the assets group and not ever put anything in there?

On Aug 22, 2013, at 12:57 AM, Yury Korolev notifications@github.com wrote:

Ok, :assets group doesn't work in production. So you should move everything out.

— Reply to this email directly or view it on GitHub.

yury commented 11 years ago

anjlab-widgets should be in same group as simple_form.

About others. If you don't generate css from scss in runtime, anjlab-bootstrap-rails and sass gems could stay in :assets group.