;) On 25/02/2009, at 7:31 AM, KtyKat223 wrote: > > No you did help. You made me think in ways I wouldn't have otherwise. > Like if you didn't mention the prob with sphinx not working, I > wouldn't have even thought to go back and undo what I had done with > the DB and sphinx. I had completely forgotten I had even done it. And > thank you for the link. I will check it out as soon as I have the > chance. For now I have to get back to the reason this server was being > setup to begin with before my friend shows up to kick my @$$ for not > being done already! > > On Feb 24, 3:15 pm, Jason Keenan <[email protected]> wrote: >> Congratulations!!!! If you look through you're emails I didn't really >> help at all by I appreciate the appreciation ;) >> >> I'd go mongrel cluster + Apache if it was me. Here's a tutorial I >> found quickly. Haven't gone through it yet to see if the tutorial's >> any good but it's the setup I would go for if I was setting up a >> rails production server. >> >> http://unixmonkey.net/?p=8 >> >> Jason :) >> >> On 25/02/2009, at 3:19 AM, KtyKat223 wrote: >> >> >> >>> No, sphinx was running. I was thinking the same thing too b/c I had >>> done the same thing before also. But,AGAIN while in the middle of >>> typing this I had an appifany (yes i know i can't spell) . I had >>> created a separate DB for production in the db.yml. But to be >>> sure it >>> worked I had specified the productin db in production.sphinx.conf . >>> Well apparently it DIDN'T work. So I set the production.sphinx.conf >>> back to using the dev DB and changed the DB.yml so that the info for >>> the development DB was listed as for production so lovdbyless would >>> use it for production (instead of the one i had told it to use >>> before). And Voila!!! Like magic it works!! All of it! Yay!! >>> After all >>> of this I think I will add a small "how-to" for others trying to do >>> this on Ubuntu so they will hopefully have an easier time than I >>> did. >>> And again, THANK YOU very much, Mr. Jason Keenan. If it hadn't been >>> for your knowledge and insight I wouldn't have been able to figure >>> this all out. I'd still be stuck with my CSS prob. And thank you as >>> well Mr. Jonathon Brennor. Now on to figuring out (or more >>> appropriately) deciding how I want apache to serve up my new >>> site. On >>> its own using fcgi, or proxy it with mongrel. Decisions, decisions. >> >>> On Feb 24, 4:29 am, Jason Keenan <[email protected]> wrote: >>>> I also had an error that wasn't the one you are having but was in >>>> Admin/users#index and related to the fact that I didn't have sphinx >>>> running. It threw a 500 error but was related to not being able to >>>> connect to sphinx (ThinkingSphinx::ConnectionError (Connection to >>>> Sphinx Daemon (searchd) failed.):), but that was in development >>>> mode. >>>> It may manifest differently in production mode. >> >>>> Jason >>>> On 24/02/2009, at 3:03 PM, KtyKat223 wrote: >> >>>>> I took a little of everyones advice. I downloaded from source and >>>>> installed everything fresh. rails 2.2.2 ,ruby 1.8.6, etc... and I >>>>> will >>>>> have you know my css prob is solved!! Yay!! Of course thats not >>>>> the >>>>> end of my woes. no I have a new error to deal with. now i can't >>>>> access >>>>> the admin area. >> >>>>> NoMethodError in Admin/users#index >> >>>>> Showing app/views/admin/users/index.html.erb where line #8 raised: >> >>>>> undefined method `f' for nil:NilClass >> >>>>> Extracted source (around line #8): >> >>>>> 5: <% @results.each do |p| %> >>>>> 6: <div class="<%= cycle('odd','even') %> search_row left"> >>>>> 7: <div><%= icon p, :small %></div> >>>>> 8: <div><%= link_to h(p.f), p %></div> >>>>> 9: <div><%= mail_to h(p.email), p.email %></div> >>>>> 10: <div><%= link_to_remote "#{ p.is_active ? 'deactivate' : >>>>> 'activate' }", {:url => formatted_admin_user_path(p, >>>>> 'js'), :method >>>>> => :put}, {:id => p.dom_id('link')} %></div> >>>>> 11: </div> >> >>>>> But I'm pretty sure once I figure this out all will be fine. If I >>>>> can >>>>> figure it out. >> >>>>> On Feb 22, 11:28 am, Jonathon Brenner <[email protected]> >>>>> wrote: >>>>>> If possible, you should always build from source. In the much >>>>>> cited "Great >>>>>> Ruby Shootout<http://antoniocangiano.com/2008/12/09/the-great- >>>>>> ruby- >>>>>> shootout-decembe...> >>>>>> ", >>>>>> compiled Ruby was twice as fast as the apt-get version. As always >>>>>> though, >>>>>> YMMV. >> >>>>>> On Sun, Feb 22, 2009 at 2:19 AM, Jason Keenan >>>>>> <[email protected]>wrote: >> >>>>>>> Here's a link (http://www.petercooper.co.uk/installing-ruby-186- >>>>>>> from- >>>>>>> source-on-ubuntu-feisty-fawn-49.html) with instructions on >>>>>>> installing >>>>>>> from source. Not sure what flavour of ubuntu you are using. This >>>>>>> one's for feisty fawn. >> >>>>>>> As far as definitely saying 1.8.6 is what you want, I can't >>>>>>> guarantee >>>>>>> that this is your issue but I can say that lovd works with this >>>>>>> version and that the errors you mentioned, with a brief bit of >>>>>>> googling, seems to be the problem. There are also an infinite >>>>>>> number >>>>>>> of possibilities in regards to what your problems might be. I'm >>>>>>> not a >>>>>>> linux guru. I personally would tend to try and find a guide that >>>>>>> other people have commented as having worked and follow it >>>>>>> verbatim >>>>>>> if I was going from scratch, but that's because I'm not >>>>>>> confident >>>>>>> about fixing up issues myself. If you are comfortable with >>>>>>> installing >>>>>>> and setting up a server with apache then half your battle is >>>>>>> won. >> >>>>>>> Jason ;) >>>>>>> On 22/02/2009, at 5:12 PM, KtyKat223 wrote: >> >>>>>>>> Srry about the multiple posting!!! My browser got "stuck on >>>>>>>> stupid" >>>>>>>> for a moment. >> >>>>>>>> On Feb 22, 1:10 am, KtyKat223 <[email protected]> wrote: >>>>>>>>> So your definitely saying it's best to go with 1.8.6 b/c >>>>>>>>> lovdbyless >>>>>>>>> isn't ready for the newer versions.? any recommendations on >>>>>>>>> the >>>>>>>>> best >>>>>>>>> place to download it from then? I wouldn't want to download >>>>>>>>> something >>>>>>>>> that could possibly be comprimised. And again, THANK YOU for >>>>>>>>> all your >>>>>>>>> help and advice!! It is greatly appeciated!! >> >>>>>>>>> On Feb 21, 11:47 pm, Jason Keenan <[email protected]> >>>>>>>>> wrote: >> >>>>>>>>>> Yes it does seem to say 1.8.7 on the rails site. It was 1.8.3 >>>>>>>>>> that >>>>>>>>>> was the problem one. >> >>>>>>>>>> Having a bit of a google around it seems that there are some >>>>>>>>>> changes >>>>>>>>>> in 1.8.7 that break some rails apps. So technically it seems >>>>>>>>>> like it >>>>>>>>>> might be a lovd-by-less problem. >> >>>>>>>>>> For lovd-by-less I think you should go with 1.8.6. I think >>>>>>>>>> there are >>>>>>>>>> some added things in 1.8.7 and as everyone migrates to 1.9 >>>>>>>>>> lovd will >>>>>>>>>> most likely go with it. >> >>>>>>>>>> Jason >>>>>>>>>> On 22/02/2009, at 2:12 PM, KtyKat223 wrote: >> >>>>>>>>>>> P.S I just saw on rubyonrails.org they're recommending >>>>>>>>>>> 1.8.7 .?.? >>>>>>>>>>> thats probably why the ubuntu repository has only v 1.8.7 . >>>>>>>>>>> But >>>>>>>>>>> if you >>>>>>>>>>> still recommend 1.8.6 I'll find and install it from >>>>>>>>>>> somewhere >>>>>>>>>>> else. >>>>>>>>>>> I'll just work on my other prob for the time being. >> >>>>>>>>>>> On Feb 21, 10:06 pm, KtyKat223 <[email protected]> wrote: >>>>>>>>>>>> just removed ruby 1.8.7 and went to install 1.8.6 . It's >>>>>>>>>>>> not >>>>>>>>>>>> there. >>>>>>>>>>>> the repository only has v 1.8.7 and apparently 1.9 . so >>>>>>>>>>>> now i >>>>>>>>>>>> need to >>>>>>>>>>>> find an outside source to download 1.8.6 . I just hope that >>>>>>>>>>>> doesn't >>>>>>>>>>>> cause probs with installing the nessesary gems. Oh well, >>>>>>>>>>>> back >>>>>>>>>>>> to the >>>>>>>>>>>> begining with trying to get it to work! >> >>>>>>>>>>>> On Feb 21, 8:40 pm, Jason Keenan <[email protected]> >>>>>>>>>>>> wrote: >> >>>>>>>>>>>>> Hi, >> >>>>>>>>>>>>> A quick look at google hinted that, as mentioned, your >>>>>>>>>>>>> ruby >>>>>>>>>>>>> version >>>>>>>>>>>>> could be causing this problem. Rails recommends 1.8.6 and >>>>>>>>>>>>> I'm >>>>>>>>>>>>> pretty >>>>>>>>>>>>> sure actually warns against 1.8.7. I found thishttp:// >>>>>>>>>>>>> www.bluehostforum.com/showthread.php? >>>>>>>>>>>>> t=13893whichisn'texactlythe >>>>>>>>>>>>> same but sounds familiar. >> >>>>>>>>>>>>> As far as making apache work with ROR, there are a >>>>>>>>>>>>> ridiculous >>>>>>>>>>>>> amount >>>>>>>>>>>>> of tutorials out there. The main problem is deciding >>>>>>>>>>>>> which one >>>>>>>>>>>>> you >>>>>>>>>>>>> want to go with. I think you'll find that your local >>>>>>>>>>>>> development >>>>>>>>>>>>> version is working because it's getting served by either >>>>>>>>>>>>> webrick or >>>>>>>>>>>>> mongrel and never touching apache. >> >>>>>>>>>>>>> Like you said, make sure your shebang lines are correct in >>>>>>>>>>>>> your >>>>>>>>>>>>> dispatch.fcgi and dispatch.rb files and make sure >>>>>>>>>>>>> your .htaccess >>>>>>>>>>>>> file >>>>>>>>>>>>> is set up properly. >> >>>>>>>>>>>>> For the css, make sure that the SITE = RAILS_ENV == >>>>>>>>>>>>> 'production' ? >>>>>>>>>>>>> 'lovdbyless.com' : 'localhost:3000' line in your >>>>>>>>>>>>> global_variables.rb >>>>>>>>>>>>> file reads SITE = RAILS_ENV == 'production' ? >>>>>>>>>>>>> 'mypublicfacingurl.com' : 'localhost:3000' so that the >>>>>>>>>>>>> browser >>>>>>>>>>>>> can >>>>>>>>>>>>> find the css file. >> >>>>>>>>>>>>> Jason >> >>>>>>>>>>>>> On 22/02/2009, at 5:50 AM, KtyKat223 wrote: >> >>>>>>>>>>>>>> While working with it I actually set all the >>>>>>>>>>>>>> permission on >>>>>>>>>>>>>> it at >>>>>>>>>>>>>> 775. >>>>>>>>>>>>>> I was going to drop them to where they needed to be >>>>>>>>>>>>>> once I >>>>>>>>>>>>>> knew >>>>>>>>>>>>>> everything would work properly. the only logs I get >>>>>>>>>>>>>> when I >>>>>>>>>>>>>> try >>>>>>>>>>>>>> to get >>>>>>>>>>>>>> apache to serve the site are the apache error log >> >>>>>>>>>>>>>> [Sat Feb 21 12:47:22 2009] [warn] (104)Connection >>>>>>>>>>>>>> reset by >>>>>>>>>>>>>> peer: >>>>>>>>>>>>>> mod_fcgid: read data from fastcgi server error. >>>>>>>>>>>>>> [Sat Feb 21 12:47:22 2009] [error] [client 127.0.0.1] >>>>>>>>>>>>>> Premature >>>>>>>>>>>>>> end of >>>>>>>>>>>>>> script headers: dispatch.fcgi >>>>>>>>>>>>>> [Sat Feb 21 12:47:28 2009] [notice] mod_fcgid: process / >>>>>>>>>>>>>> var/www/ >>>>>>>>>>>>>> lovdbyless/public/dispatch.fcgi(5130) exit(communication >>>>>>>>>>>>>> error), >>>>>>>>>>>>>> terminated by calling exit(), return code: 255 >> >>>>>>>>>>>>>> and once in a while in the fast cgi crash log in the >>>>>>>>>>>>>> lovdbyless >>>>>>>>>>>>>> logs >> >>>>>>>>>>>>>> # Logfile created on Fri Feb 20 15:42:52 -0500 2009 by / >> >> ... >> >> read more ยป > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lovd by Less" 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/lovdbyless?hl=en Who loves ya baby? -~----------~----~----~----~------~----~------~--~---
