On 14/09 02:28:22, Mike Leahy wrote: > Hello list, > > I've got a project that I setup with subversion and trac on a personal > machine - I'm now moving it to another server, but I don't seem to be > able to get trac to work on the new server
What type of server are you using? tracd or apache/CGI or apache/mod_python or...? > (it give me a "500 Internal server error" when I try to access the > web page on the new server). What does it say in the logs? I think you need to enable logging in the trac.ini if you're using tracd, not sure with apache. You'll probably work out the answer straight away after enabling the logs and having a look. My usual guess for this sort of thing is that Python can't find the svn-python libs (or they're not installed). > Basically, I have two folders called /var/www/projectname/svn and > /var/www/projectname/trac Just a minor tip from my own experience with structuring things that way - it can end up being a pain if/when you've got more than one Trac (eg. a different Trac repo in /var/www/proj2/trac) - because both of the projects are in a directory called "trac", they clash. Or maybe that was just if you're running them both under the same tracd. Hmm. Can't remember. But anyway, I used a fairly simple workaround - created a directory something like /var/www/trac-projects, then put soft links in that - eg. proj1 -> /var/www/proj1/trac , proj2 -> /var/www/proj2/trac , etc. And then exclusively refer to those Trac repos via the /var/www/trac-projects/$PROJ path. > - everything is configured and works fine on the original machine - > after I setup the new server, I just copied these folders and the > httpd configuration to the new server. The subversion repository > works fine on the new machine. Yeah, subversion has slightly fewer moving parts, and hence needs slightly less babysitting. :) > (both machines have trac 0.10.4. Installed the same way? From source or packages? > I'm guessing the problem has something to do with the different > IP/URL on the new server, but I haven't found the documentation that > describes what I should do to make the appropriate changes to the > trac setup, There's a setting in the trac.ini where you should specify the URL to access this instance of Trac, but I don't think that's particularly important - and certainly shouldn't lead to the error you're having. > or maybe there is a more appropriate way to move the installation? Not really. I think what you've done should work fine - if nothing else was going wrong. But it looks like something is. :) > Thanks in advance for any advice. > Mike Pete. -- http://flooble.net/blog "I'm sorry but if you feel like your faith is being attacked, well... you're right. But not only that, your faith *should* be attacked. It should be mocked and laughed at. It should be held up to the harsh light of logical scrutiny and exposed for what it is: crazy talk." -- riffraff2001, http://www.alternet.org/story/36195 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
