Version Control and USB ninja sticks
-
For maintaining multiple copies across machines, frequent moving between PCs, dev environments, mobile work etc, has anyone seen a tool that does an easy "plug and play"-like sync for source code on flash disks? I think, not sure, there was a CP guy that did some experiments for fun, not sure whether it was with SVN or similar but it allowed an easy to use 'mobility' with source control. I am looking at single dev/person tool, no teams, wouldn't mind if it is a bit rough.. Just something that easily, auto-magically if possible, backs-up and syncs all the prototype work across multiple environments and PCs without much hussle to set up (aka agile fragile).
-
For maintaining multiple copies across machines, frequent moving between PCs, dev environments, mobile work etc, has anyone seen a tool that does an easy "plug and play"-like sync for source code on flash disks? I think, not sure, there was a CP guy that did some experiments for fun, not sure whether it was with SVN or similar but it allowed an easy to use 'mobility' with source control. I am looking at single dev/person tool, no teams, wouldn't mind if it is a bit rough.. Just something that easily, auto-magically if possible, backs-up and syncs all the prototype work across multiple environments and PCs without much hussle to set up (aka agile fragile).
User of Users Group wrote:
I think, not sure, there was a CP guy that did some experiments for fun, not sure whether it was with SVN or similar but it allowed an easy to use 'mobility' with source control.
I did that, not sure if I mentioned it. It works quite well, just make sure your USB stick is configured as the same drive letter on every machine. It was a bit slow though :|
xacc.ide - now with IronScheme support
IronScheme - 1.0 alpha 2 out now -
For maintaining multiple copies across machines, frequent moving between PCs, dev environments, mobile work etc, has anyone seen a tool that does an easy "plug and play"-like sync for source code on flash disks? I think, not sure, there was a CP guy that did some experiments for fun, not sure whether it was with SVN or similar but it allowed an easy to use 'mobility' with source control. I am looking at single dev/person tool, no teams, wouldn't mind if it is a bit rough.. Just something that easily, auto-magically if possible, backs-up and syncs all the prototype work across multiple environments and PCs without much hussle to set up (aka agile fragile).
User of Users Group wrote:
For maintaining multiple copies across machines
I use Subversion (SVN) and syncback. Using the advanced tabs under syncback I have listed .svn directories as skipped. This allows me to sync the source only, and maintain the same source on seperate instalations of subversion on two different machines that do not talk to each other except by USB.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
User of Users Group wrote:
For maintaining multiple copies across machines
I use Subversion (SVN) and syncback. Using the advanced tabs under syncback I have listed .svn directories as skipped. This allows me to sync the source only, and maintain the same source on seperate instalations of subversion on two different machines that do not talk to each other except by USB.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Hmm.. cheers Ed, first time I see Syncback so I started Googling for it. Would that (and is that all that is required) be failsafe and fully featured source control for work done on seperate boxes? Say there's 5 boxes, you work in rotation (or round batman if you prefer :) between them, evenings/weeks apart, no connectivity between them, modifying source as random as it gets because each has say different hardware capabilities, different environment installed, so you cover different aspects of code as you get to quirks on specific boxes. Of course you want one and all sources to it to come from the stick, before/after each time you touch/leave any of those PCs; I need it to behave as a medium for storage of all revisions as well as sync, that considering each box will have its own SVN or, what was it, berkeley db storage.. For that kind of work to be maintainable would your method behave or provide all the SVN features as if there was a single repository (assuming you command the insert/removal of flash before accessing the current machine SVN)? Not sure whether omitting .svn directories would provide for this scenario. Thanks Leppie, did a quick search but couldn't find anything. Would welcome a rough idea.. Pretty sure I was aiming at another guy, some geezer with a pic on which he looked, well pretty drunk and rough :), seemed very/too relaxed about PCs and hitting his website mentioned something about it being overwhelmed for that particular download. Must have been years ago, and it probably is not exactly what I am after, and he had some real odd articles over here.. Where's that search facility for media meta/tags and does anyone decorate those ? :-) Would take everything on, just to see if it would boost productivity and maintainability of some experimental pieces..
modified on Tuesday, March 25, 2008 2:57 PM
-
Hmm.. cheers Ed, first time I see Syncback so I started Googling for it. Would that (and is that all that is required) be failsafe and fully featured source control for work done on seperate boxes? Say there's 5 boxes, you work in rotation (or round batman if you prefer :) between them, evenings/weeks apart, no connectivity between them, modifying source as random as it gets because each has say different hardware capabilities, different environment installed, so you cover different aspects of code as you get to quirks on specific boxes. Of course you want one and all sources to it to come from the stick, before/after each time you touch/leave any of those PCs; I need it to behave as a medium for storage of all revisions as well as sync, that considering each box will have its own SVN or, what was it, berkeley db storage.. For that kind of work to be maintainable would your method behave or provide all the SVN features as if there was a single repository (assuming you command the insert/removal of flash before accessing the current machine SVN)? Not sure whether omitting .svn directories would provide for this scenario. Thanks Leppie, did a quick search but couldn't find anything. Would welcome a rough idea.. Pretty sure I was aiming at another guy, some geezer with a pic on which he looked, well pretty drunk and rough :), seemed very/too relaxed about PCs and hitting his website mentioned something about it being overwhelmed for that particular download. Must have been years ago, and it probably is not exactly what I am after, and he had some real odd articles over here.. Where's that search facility for media meta/tags and does anyone decorate those ? :-) Would take everything on, just to see if it would boost productivity and maintainability of some experimental pieces..
modified on Tuesday, March 25, 2008 2:57 PM
User of Users Group wrote:
Say there's 5 boxes, you work in rotation (or round batman if you prefer between them, evenings/weeks apart, no connectivity between them, modifying source as random as it gets because each has say different hardware capabilities, different environment installed, so you cover different aspects of code as you get to quirks on specific boxes.
hmmm... in your environment you might want to consider one SVN directory, on your stick. Yes, on your stick. Each machine would submit and request from the local svn database of the stick and allow you to come and go as you please from machine to machine. Mine is specifically so I can have multiple svn servers. the stick is the medium between the two. It is redundant backup of sources with history on each.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)