Hi Warren, On Aug 26, 2015, at 5:28 PM, Warren Young <[email protected]> wrote:
> On Aug 26, 2015, at 2:12 PM, Lonnie Abelbeck <[email protected]> > wrote: >> >> we wondered if it could be used to track changes to these configuration >> files in a way a non-developer type could easily understand. > > Did you look at etckeeper, and if so, why did you reject it? > > https://joeyh.name/code/etckeeper/ I had not heard of etckeeper before, but seems to work around package managers, we don't have any. The code we implemented to manage the "fossil commit" is quite small, we did not include any version control binary on our image until we added Fossil. Our images are like "firmware" and size matters, currently around 50 MB compressed. > >> Long story short, success, Fossil is a gem ! > > Glad to hear it! I’m sure there many Fossil users who can’t or won’t tell > how and why they are using it, so it is nice when someone decides to step out > of the shadows. > >> Since any HTTPS access to /admin/fossil/ is authenticated by lighttpd, we >> set Fossil's "nobody" permissions to "a" (admin) and add the "admin" user >> for "s" (setup) permissions. > > Why? Does doing one require the other, or does it merely *allow* the other? > > It seems to me that you had an opportunity to construct some defense-in-depth > here, but chose instead of replace one defense layer with another, so that > you still have a single point of failure. AstLinux has it's own web interface (PHP), we run Fossil's web interface within an HTML iframe. We do the same for Monit, Darkstat and phpLiteAdmin . This allows for one common set of admin credentials to access these services. > >> (Yes SourceForge SVN, our project is over 10 years old, old habits die hard >> :-) ) > > What with your newfound Fossil love and SourceForge turning evil,[1] maybe > it’s time to consider self-hosting your project in Fossil. > > I documented my process for migrating a 15-year-old svn repo to Fossil here, > which has some advantages over the method described on the Fossil pages: > > http://goo.gl/Zr6YQw > > The attached script will require some local adjustment, but the code should > be clear enough to make that straightforward. Thanks for sharing ! I'm sure that day will come. :-) Lonnie _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
