On May 24, 2011, at 8:33 AM, Derek Atkins wrote: > John Ralls <[email protected]> writes: > >>> If at all possible, I would recommend to initiate the sync action as >>> part of an svn post-commit hook. I realize this may not be easy >>> because two different people manage the involved repos on independent >>> servers. >> >> We could set up signaling somehow, but it would be easier to just move >> the whole thing to Code. Derek? > > Either is possible. We could set up a port-knocker to signal you when > there's an SVN commit. (We already do this to update www when htdocs > gets updated). > > As for moving the whole thing to Code, I think it would be better to > wait until Code gets updated to a more recent version of the OS. It's > currently running Fedora 10. Fedora 15 was just released today. I > should have time to actually update the system starting next week so I > can schedule the maintenance. It will require several hours of downtime > to perform the upgrades. > > Once I perform the upgrade we could move the git sync to the server. > Down the road we could still consider migrating from SVN to GIT > completely? > I think Geert, Christian, and I are ready to do that now. Not sure about the others. Perhaps you'd want to do that as part of upgrading Code?
>> In the meantime, I'll increase the frequency of updates. > > Or we could set up the port knocker (which I could do sooner). What kind of listener will I need? Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
