Dwight Shackelford wrote: > > Well, cookbook is not one I wrote, but sometimes it is the only one > Mongrel will start for. I just thought that it started Mongrel. Didn't > know it was starting it specifically for a certain subdirectory. > > What is the mechanism behind that? What do I check to see where Mongrel > is listening? > > I started two weeks late into a 5 week class. What you're witnessing is > thrashing.
Start here: http://www.tutorialspoint.com/ruby-on-rails/rails-introduction.htm READ it all. It is old and out of date, but is so generic that this barely matters. Then, either set up a Rails project from scratch following the tutorial or connect with somebody that has at least a passing familiarity with the framework and have them do it with you. If mongrel will not start for any project other than cookbook then your problem is that each of the other projects has a fatal error that prevents the server from starting. When this happens the cause is sent to stderr which, if you are starting it from a virtual terminal session, will be your display. Follow the stack trace to locate the problem. But, do the tutorial first. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
