On 9/15/05, Attila Kinali <[EMAIL PROTECTED]> wrote: > On Wed, 14 Sep 2005 11:17:54 +0200 > Lourens Veen <[EMAIL PROTECTED]> wrote: > > > Victor Pracht: "Just store a text file in a version control system. If you > > want to get fancy, check it in as binary, so that all conflicts get reported > > and sequential editing is enforced." > > I would go for this option. The reasons are that it's very simple, does > not need any special tools to access it, can be easily backed up and > replicated and all conflicts are either resolved by svn or the commit > is rejected. The only draw back i can see is, that you cannot prevent > deleting automaticaly (unless svn has an option to set files > to append only).
My preference is to start small but convenient and work up from there. For a while, we won't need more than one server, and it's easy enough to make PHP and MySQL identify duplicates. ASCII backups are easy enough. They can be exported to the local server every time someone commits a new part number, and we can also have the PHP script email new commits to a mailing list. That would be overkill for now, but it would also be a nice place to start for small companies. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
