I would argue that this would be a great feature to have. We
regularly send people out on ships. We end up with mixed
collaboration between groups on and off the net, so syncing would be
a huge help... if we stick a couple engineers on a ship for a month
it is no fun to try to manually get things back in order when they
next get to an access point. Need to figure out the same kind of
deal with svn. It's still pretty uncommon to have decent bandwidth
on ships.
If there was a way to extract the differences between some fork time,
then we could compress that and send it over the periodic sat
connections without bringing down the wrath of sat time charges.
That would be huge.
-kurt
On May 15, 2006, at 1:51 PM, Patrick Stinson wrote:
How many tickets do you historically add on the laptop before you
would want to sync?
One could argue that the most useful part of trac is the collaboration
part, not the storage part. That is, when you are on the road and
adding tickets, the tickets never change, so you could just use a text
editor with copy and paste them when you get to a connection. I am
quite active with my trac instance 'on the road' and I just add the
title and description in a TODO file, and the other ticket fields,
however many you use, are usually self-explainatory upon addition to
trac anyway.
Just a thought.
On 5/15/06, Robert Gravsjö <[EMAIL PROTECTED]> wrote:
Kfir Lavi wrote:
> Hi,
> I'm working with trac in my laptop.
> Now I want to put trac on the different computer - server.
> I don't have constant internet connection, so I'm searching for
a way
> to sync the repository of the laptop with the server and vice
versa.
> Is this possible?
Yes it is possible, but I have yet to see a solution for it. Syncing
this way is not a trivial task.
>
> Again, the problem is that users will create new tickets at the
server
> and I will create new tickets at the latptop.
Could probably be done by comparing db dumps, manipulate the
laptop data
before updating the server and finaly refresh the laptop db with a
copy
of the server db.
New tickets would be fairly simple I think and could be done
through the
ordinary API. Changes and updates I'm not to sure of, but I assume
you
could use the API for this too.
Feature request maybe? Wonder how common this scenario might be
nowdays.
Used to be a huge issue in "those days".
My 2c,
roppert
>
> Thanks,
> Kfir
>
>
>
---------------------------------------------------------------------
---
>
> _______________________________________________
> Trac mailing list
> [email protected]
> http://lists.edgewall.com/mailman/listinfo/trac
--
RobertG
Phone: +46 (0)480 44 58 35
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
--
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
