My hobo development site is getting very big and very slow. I wanted to
see what difference I could expect when it went into production mode
(and to give the beta testers a break), so I tried a very simple
experiment. I changed database.yml so that the production database
pointed to the development data, figuring that the existing development
data could be used as a mock for the production data. (I used this
trick in RoR in the past with no difficulties).
I started the server using
/prompt: rails server -e *production.*
/
but it started with:
/=> Booting Mongrel
=> Rails 3.0.3 application starting in *development *on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
/
tried: rails server -e "*production" *with the same result.
There's more than one way to skin this cat:
/prompt: export RAILS_ENV="*production*"
prompt: rails server
=> Booting Mongrel
=> Rails 3.0.3 application starting in *production *on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
/
Cool! (or so I thought). Switched to the browser, hit refresh and there
was my site with absolutely NO formatting and the javascript thingys
didn't work. Anything not javascript worked, but still no formatting.
Looked at the terminal output and found many error messages in the form of:
/Started GET "/stylesheets/reset.css?1302614751" for 127.0.0.1 at Fri
Apr 22 19:54:39 -0400 2011
ActionController::RoutingError (No route matches "/stylesheets/reset.css"):
Rendered
/usr/local/lib/ruby/gems/1.8/gems/actionpack-3.0.3/lib/action_dispatch/middleware/templates/rescues/routing_error.erb
within rescues/layout (8.0ms)
Started GET "/hobothemes/clean/stylesheets/clean.css" for 127.0.0.1 at
Fri Apr 22 19:54:39 -0400 2011
ActionController::RoutingError (No route matches
"/hobothemes/clean/stylesheets/clean.css"):
/
Similar messages were there for the remaining css and javascript files
as well.
Remember, I made a *one-word* change in database.yml and switched to
*production *mode, nothing else. Returned to RAILS_ENV="development"
and all was back to normal.
Searched the web for potential causes and/or solutions, but found none.
Ideas anyone?
Don Z.
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hobousers?hl=en.
