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 this > http://www.bluehostforum.com/showthread.php?t=13893which isn't exactly the > 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 / > > [20/Feb/2009:15:42:52 :: 13156] starting > > [20/Feb/2009:15:42:52 :: 13156] stopping gracefully > > [20/Feb/2009:18:59:29 :: 25203] starting > > [20/Feb/2009:18:59:29 :: 25203] stopping gracefully > > > And when i say server Yes it is one I'm setting up my self. It belongs > > to a friend of mine and I'm doing this as a favor for him. It's an > > actual rack mount server. A little older model but it is a very nice > > one (more than enough for what he'll be using it for) and it was still > > in the box unopened when he got it. Right now it works fine with > > everything he needs on it except for an error in a part of the online > > store thats on it. but while I was figuring that out I was fooling > > around with this for the space on the server i get to use. It is a > > complete fully functioning web server (except for the ecommerce site > > till I figure that 1 lil prob out). But as I said earlier, this is the > > first time I've done anything with ROR. and any advice is more than > > welcome. Especially since I have found extremely little info anywhere > > about getting ROR to play nicely with apache. As far as being explicit > > I'm not sure what info your looking for although I'm pretty sure, > > while I was typing this, I just found the reason rails won't start. I > > Just realized that the place the dispatch.fcgi header is pointing to > > doesn't exist. I just need to find where ruby is on this machine and > > point it there. Hopefully that will fix the rails failing to start > > prob. because when i run the command > > > ruby dispatch.fcgi > > > the output is "perfect" if there is such a thing. I wonder if that > > might be why the CSS wont work in production? or from a client even > > while in developement? > > > On Feb 21, 9:15 am, Jason Keenan <[email protected]> wrote: > >> Hey there, > > >> Check the log to see if there is anything there. I had some problems > >> with the latest version of rails too. With a failed to start message, > >> nothing in the logs though cause, funnily enough, it fails to start. > > >> For the CSS, make sure you have your production domain set in > >> global_variables.rb > > >> For the failed to start bit, make sure you have the correct > >> permissions set on the files. All the folders should 755 and files > >> should be 644 except dispatch.fcgi from memory which should also be > >> 755. I installed straight from git and there were unfortunately some > >> permission glitches. You will also need to adapt your .htaccess file > >> in the public folder to suit your setup. > > >> When you say 'your server', is this one you've set up yourself from > >> scratch or a hosting service. If you've set it up yourself then > >> you'll have some fun getting it working easily. If the latter, the > >> tips above might help. You probably need to give a more explicit > >> description of what you are doing or have done. > > >> Jason :) > > >> On 21/02/2009, at 4:26 PM, Steven Bristol wrote: > > >>> On Fri, Feb 20, 2009 at 9:14 PM, KtyKat223 <[email protected]> > >>> wrote: > > >>>> I guess it's my turn to finally ask a question. After all I did > >>>> figure > >>>> out everything else on my own! It took me two days of > >>>> workarounds to > >>>> install everything I needed to run LovdByLess on my server. I > >>>> have it > >>>> running fine in development mode while accessing it on the > >>>> localhost. > >>>> But when I run it in production mode the CSS doesn't work. Also > >>>> if I > >>>> try to access it on the network even in development mode the CSS > >>>> doesn't work. I just can't seem to figure it out. Any ideas > >>>> would be > >>>> helpful. This is my first time working with ruby and so far has > >>>> been a > >>>> great learning experience. The only other problem I have is my > >>>> Apache > >>>> server won't serve the site. I just get the error saying rails > >>>> failed > >>>> to start. But that is not a problem that anyone here will help me > >>>> with. Just in case it might help I'm running... > > >>>> Ubuntu Server 8.10 > >>>> rails 2.2.2 > >>>> gem 1.3.1 > >>>> ruby 1.8.7 (2008-08-11 patchlevel 72) [i486-linux] > >>>> Apache 2 > >>>> and many others > > >>>> If you need any other info just ask. Thanks in advance for any > >>>> advice. > > >>> What's the link to your production site. There is most likely > >>> something wrong with your pathing on the css issue. > > >>> As far as the non starting issue, I've never run lovd on 1.8.7. > >>> We use > >>> 1.8.6. What are you using in dev? I would suggest not using 1.8.7 as > >>> it's a bit buggered. > > >>> cheers, > >>> steven bristol --~--~---------~--~----~------------~-------~--~----~ 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? -~----------~----~----~----~------~----~------~--~---
