Got it. Then the question is what in your opinion consitiutes a "state" for your project?
Say, in case of a development project it may be a buildable collection of source-files (which may include some binary artifacts used as sources). This "state" is then being versioned in time, and Fossil takes charge of tracking the "state" changes. Storing binary data in Fossil gives little utility as it's not diff'able in a meaningful form, apart from the fact that it won't scale. So in your case, I would try to come up with some sort of a meta-project that __references__ sources, configuration, and output data-sets(?? SQL-queries). Then version this meta-project as it progresses through the trials and experiments. I would keep the output artifacts stored in bulk elsewhere (DBMS, cloud, NAS etc.) The meta-project then becomes the entity that ties all pieces together, and its timeline may then be branched, tagged, etc. Additionally, if Fossil indeed has to handle it all, you may use Fossil's wiki system (versioned) to keep these "state"-transitions/conclusions described more in-depth. This way Fossil will be able to tell you what has changed from one "state" vs. another by listing the diffs of such a "meta-project". Makes sense? On Sun, Oct 23, 2016 at 5:13 PM, Scott Doctor <sc...@scottdoctor.com> wrote: > > On 10/23/2016 13:59, Artur Shepilko wrote: > >> It's not clear what type of project the OP is trying to setup, whether >> it's a programming-related project, or general document-repo type. >> >> I am doing research where we may do a dozen iterations a day generating > about 10-100MB of files per iteration. within a short period of time we > will have well over a terabyte of information. My current workflow uses a > database (was filemaker but switched to sqlite a while ago) like a library > card catalog with notes and status fields. The files are a combination of > analysis code, text csv, binary, and documentation. Occasionally we find > something and want to go back to older data and re-run the experiment with > a few tweaks, or modify the analysis program. I have information overload > and finding stuff, even with it cataloged in a database, is becoming a > significant chore. So I am trying out different techniques, such as using > fossil, to track the experiments and the large volume of information. > > ------------------------- > Scott Doctor > sc...@scottdoctor.com > ------------------------- > > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
