Never mind. Had a brain fart and didn't clear the cache. It's working now. On Thursday, February 14, 2013 1:28:03 PM UTC-7, Roque Burleson wrote:
> Hi, > > The front end guys on our team have opted to use Bootstrap and it looks > great on their development boxes. When I move it to our production server > it goes back to the view without the bootstrap changes. > > On the same production server if I start the application using "rails > server" instead of the Apache Web Server I get to see all the Bootstrap > modifications again. I'm wondering is their some extra configuration that > needs to be performed to get it to work on Apache Web Server using Phusion > Passenger as our middleware. > > Rails 3.2.11 > Ruby 1.9.3 > Passenger 3.0.19 > Apache > > Gemfile > source 'https://rubygems.org' > gem 'rails', '3.2.11' > gem 'devise' > gem "nested_form" > gem 'mysql2' > group :development, :test do > gem 'rspec-rails', '2.11.0' > gem 'annotate', '2.5.0' > end > # Gems used only for assets and not required > # in production environments by default. > group :assets do > gem 'sass-rails', '3.2.5' > gem 'coffee-rails', '3.2.2' > gem 'uglifier', '1.2.3' > # Gems added for bootsrap > gem 'therubyracer' > gem 'less-rails' > gem 'twitter-bootstrap-rails' > end > gem 'jquery-rails', '2.0.2' > group :test do > gem 'capybara', '1.1.2' > gem 'factory_girl_rails' > end > -- You received this message because you are subscribed to the Google Groups "twitter-bootstrap" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
