On Tue, Nov 17, 2015 at 6:06 PM, Dömötör Gulyás <dognot...@gmail.com> wrote:
> Unfortunately the corporate network in this case is rather conservative, > and I can't have a server running, plus I can't even connect my main dev > laptop to the corp network... rather silly, the whole thing is. > ... > > So all in all fossil is great for doing field work and keeping track of > tickets etc offline, but I don't have a decent way of syncing. Of course, > each dev could upload their fossils to the windows share, and pull from > each other to a local repo, but that quite sounds like a bad n-way merge > waiting to happen. > If every dev has a separate dev laptop, you could sync to each other using a cross-over ethernet cable (if your laptops don't have ethernet ports, you can get USB ethernet adapters). That would save having to copy between your dev and "office" PCs to share your work. Since your dev laptops are not connected to the company LAN, running the Fossil server would not touch the company network. Once company I used to work for, software dev PCs were connected to an isolated LAN. IT provided basic support of the LAN itself, but we were responsible for PCs connected to it. If we messed up a PC, the most they would do is re-installed Windows. If there was a hardware failure, IT would repair or replace it. The tools and other software we used on the dev PCs were our responsibility. Moving documents and product software in/out of the dev LAN required "sneaker net", but at least we had network connectivity between our dev PCs.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
