Might also be worth considering something like Salt (or equally Puppet /
Chef etc) as well which can manage the config and push it down. Coupled
with GH for version tracking it, this would also mean you could deploy
software + a set of changes to the target machines all at the same time,
which might held with consistency...
On Sunday, September 2, 2012 12:11:11 PM UTC+10, andyg (@geekscape) wrote:
> hi Stuart,
> On 2012-09-1 12:15 , Stuart Young wrote:
> > FWIW: If anyone creates and/or changes profiles for slicing or control
> > software for either the Prusa or the Cupcake, then these configs need
> > to duplicated somewhere onto the other laptop (do NOT overwrite
> > existing configs), so that if this sort of situation happens again,
> > the Prusa laptop could be used to drive the Cupcake, and vice versa.
> > We'll need to sort out some sort of location for this stuff to reside,
> > as well as a naming convention to avoid clashes.
> Your suggestion of using GitHub makes sense.
> Freely available, distributed source (configuration) control.
> -O- cheers = /\ /\/ /) `/ =
> --O -- http://www.geekscape.org --
> http://twitter.com/geekscape --