On Thu, Aug 8, 2013 at 10:48 PM, j. van den hoff <veedeeh...@googlemail.com>wrote:
> 2. > I'm not comfortable with categorically recommending to new users to > separate the database from the checkout. I know that many on this list > think this to be a good thing but in general In fossil keeping them in the same dir can and does lead to user error. Here's a concrete example which i've done more than once while doing old-school refactoring: perl -i -pe 's|func_name|new_name|g' * fossil commit -m ... fatal: not a checkout ??? Oops - i just filtered through my _FOSSIL_, corrupting it. The same is even easier to do on a repo db because they will match "safer" wildcards like *.*. (i've done that on SVN repos several times, too, when using find(1) in conjunction with perl.) Yes, silly me - it's my fault, not fossil's. But now that i've done that more than once i know better than to keep my repo and checkout together, and i wholeheartedly convey that advice to you :). i _strongly_ recommend against keeping the repo db in the same dir as a checkout. Very little can go wrong when they're separated and lots can go wrong when they're not. For CGI/server modes, there's a related point: the dir containing the repo must be writable by the CGI/server process, and it's often possible (and always preferable, from a security point of view) to place the db outside of the webroot, in a dir owned by the CGI user (the account holder, for most providers). This keeps the repo from being inadvertently directly downloaded (as opposed to cloned, which has fewer security concerns). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
