On Sun, Dec 27, 2009 at 11:37 AM, Christian Johansen <[email protected]> wrote: > Hi Ben, > How are you running the application - through passenger? Your logs should > have some clues for you, are you checking the right logs? (i.e., right > environment). I'd suggest running the app with mongrel or thin in > development mode to more easily follow along when Gitorious fails. There > might also be a problem with the permissions on the log directory, you need > to make sure that the user running the process can write to the log > directory. When running Passenger, it is the user who owns environment.rb > that owns the process. Following my guide, that should be the git user.
Hi Christian. Thanks for the guide. I finally made it now. To answer your questions anyway and to help other people struggling with this: Yes, I ran it through passenger at that time (first tried it with mongrel, same results). The logs showed nothing as far as I can tell and I really spent a couple of hours with nothing but this issue. It turned down to be a problem with the cookie vs. domain. I _did_ set both the hostname and the gitorious host to the same name "foobar" but somehow that didn't work. Changing both (identical) values to "foobar.local" did the trick. I've no idea why and how, but this seems to work now. Thanks for your response and regards, Ben -- You received this message because you are subscribed to the Google Groups "Gitorious" 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/gitorious?hl=en.
