[fossil-users] Limiting cruft in my repos

I've described before how I use fossil to manage student assignment submissions in courses I teach. A perennial problem is that the students commit binary executables, .o files, and the like. Theses change every build so I have dozens of versions of potentially large files in the student repos.

[fossil-users] Unversioned content for distribution

I have a fossil repo and in it I have a file foo.js that is generated by my build process - so I don't want it versioned. But I *do* want it distributed, and want it referencable from foo.html - which *is* versioned. foo.html and foo.js are *not* served by fossil, but by a simple apache or nginx

[fossil-users] Fossil Hosting by Generic PHP Hosting Services

Date: Sun, 23 Apr 2017 15:25:54 -0700 From: Richard Hipp > To: "Fossil SCM user's discussion" >... > wrote: >> Hey there, >> I currently know of two Fossil hosting systems, Flint and Hydra. > I'm going to take this in a different direction and