On Jan 26, 1:57 am, Simon Martin simon.jk.mar...@gmail.com wrote:
I would upgrade Trac from 0.9 to 0.11 on the Linux machine first
Thanks, this is good advice, I can see why it is worth doing - and I
hadn't thought of it.
When moving from Linux to Windows I see no specific problems, just
P.S. @Matt: If you don't want to help with Windows issues, why do you
answer at all? :)
To clarify my original response.
The first of which is that my experience is that Windows gets no love
from the open source community and you'll most likely get less
responses, that is a big deal when the
To add to the wall of text, keep in mind that when I say shut down
the app --- remember Trac is a web app. If you have control over DNS
or the web server itself, then you can easily make it so people can't
pop in and change anything while you are working. But if you don't
shut down SVN as well,
On Mon, Jan 26, 2009 at 5:57 PM, Vincent Polite
vpol...@socialnetconnect.com wrote:
Lots of good advice
Vincent
Thanks for all the info. I'll read careful and digest.
Some of this falls into presenting a case - there are issues outside
our limited IT department that are driving the idea of
On Jan 24, 9:21 pm, Flatfender flatfen...@gmail.com wrote:
I would have to ask why you *need* to migrate from a Linux server to a
Windows one? Also I would not migrate databases until you had it
working on the new server. Only try to change one thing at a time,
that will make it easier
Hi,
Please note: I haven't done such a migration yet, these are just my
thoughts! Other members of this mailing list may have more experience.
I would upgrade Trac from 0.9 to 0.11 on the Linux machine first, see:
http://trac.edgewall.org/wiki/TracUpgrade
I'm a Linux guy, so this is biased. :) But my experience with almost
every open source app I've used/installed as a sys admin, is that very
few people put much effort into answering questions about
install/config problems on windows. Just b/c LAMP has windows
counterparts and can work doesn't
