Bingo! I fixed the permissions problems with your command above (using user/group ruby) and the site loaded. Only it loaded the blank white page with the big pink graphic and the text fields.
I played around with the .rb files and changed things that said "localhost:3000" to my domainname (sub.domain.com) and restarted apache and everything looks normal now! Not sure if that was a good idea or not - I am still new to both Ruby AND Linux... But NOTHING links to port 3000 anymore, so while it may "LOOK" like it is working - I might have ruined my setup for when I want to serve PRODUCTION instead of development. Not sure what, but I figured I needed to get rid of :3000 in the entry since I am serving my application using APACHE which runs on port 80... Still trying to make since of all of this and plan to research some more - but I WANTED SOME SORT OF RESULTS so I could at least have some sort of motivation for learning all of this! So far I am very happy and interested to learn more. THANKS FOR YOUR HELP ALONG MY WAY! On Nov 2, 4:06 pm, Steven Bristol <[email protected]> wrote: > On Mon, Nov 2, 2009 at 4:48 PM, Chad <[email protected]> wrote: > > > Hey Steven, > > > Sorry for my ignorance, but again I am new to linux. During the > > installation I setup a user "ruby" (not chad) but since I had to type > > "sudo" all the time during the installation of ruby, mysql, nginx etc > > --- the 2nd time I installed I stayed logged in as root so the > > commands were simpler to pass to the system (I reformatted and started > > over with apache instead of nginx). > > > Was that a bad idea, and will I need to reformat and reinstall > > everything (as regular user and NOT root?)? > > > I know I have a user named "ruby" with sudo ALL=ALL privelages but I > > do NOT know what the MAIN group name is? shouldn't APACHE run as user > > www or something? > > > Thanks for your help. > > > ~Chad > > Probably the group name is also ruby. If you do> ls -al ~ > > you should see the user name and the group name for the files there. > Just use whatever it says. > > Apache will run properly, don't worry about it, it is properly > configured. You probably don't need to delete everything, most likely > changing the ownership of the app dirs/files will fix the problem. > > cheers, > steve --~--~---------~--~----~------------~-------~--~----~ 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? -~----------~----~----~----~------~----~------~--~---
