Jason,
Well, I did some searching and found some 2007 and 2009 post in which
someone did the same thing as me. Everyone that responded said that he
should just "rm -r /some/wrong/location/myproject"
During initialization, the 'trac-admin /some/wrong/location/myproject
initenv' went fine and w/out errors. But the "Available Projects" page
didn't list the new project, so that's how I knew I had "done gone and
did sum'thin wrong."
So, the only thing I'm concerned now about is if /some/wrong/location/
myproject is hard-coded somewhere in some file even though I've
removed it manually.
Which begs the question, what if I had installed a new project in the
correct location and been recognized by the Available Projects page,
is this any different? The procedure for removing an install the same?
I was unable to find a trac.conf file in my apache directory so
apparently I'm just running plain Apache w/cgi. I remember seeing a
Trac FAQ a few days ago in which a question was asked, "Why is Trac so
slow?" The answer had something to do with "Do you have python/wsgi
enabled because conventional cgi is slower." I have not yet graduated
to that Trac expertise yet and I'm just taking is one step at a time.
Nevertheless, I've re-initialized the new project in the proper place
and it's working fine.
One other thing I was concerned about is if my original project
creation (wrong location one) had a svn repo listed in its trac.ini
would installing a new Trac project (with same name) potentially cause
any syncing issues with svn since both would be pointing to the same
svn repo. This is why I wanted to remove the old one before I started
creating a new one with the same name.
On Thu, Apr 14, 2011 at 12:02 AM, Jason Miller wrote:
I created a temp trac environment and then moved the created trac
environment to a new location with out issues...
mkdir /some/wrong/location/myproject
trac-admin /some/wrong/location/myproject initenv
woops! wrong location :)
cd /some/wrong/location
mv myproject trac/
Though I was using the tracd to host the temporary site. And
depending
on when you found out when you made the mistake, and if your using
Apache/IIS, you will have to edit your;
Apache trac.conf file : /etc/apache/conf.d/trac.conf (or
equivalent)
The python/wsgi initialization file (if your using wsgi) located
in
the htdocs directory
I have no idea what other file to edit/modify if your not using
wsgi.
I can only imaging there is an environment variable that you will
have
to adjust as well when using CGI or modpython.
The good news however, I did 'not' have to edit the actual
trac.ini
file, or any other file within the 'myprojects' directory except
the
wsgi file. Literately; I simply moved it, and told everyone else
where
it was. (granted I made no changes to the trac.ini file after I
created the initenv)
Hope this helps! If not, if you could tell me how your running
Trac, I
can simulate it on this end and let you know what I find that
might
work for you.
Jason
--
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.
