Yes, thanks; I know about that, but that's too coarse-grained for my needs.
In this case, I have a project I want to be *non-public* altogether, but I also don't want some people to have access to everything, and I can't put everything in the wiki. The current permission system works well, but not for this kind of scenario. On 01/15/2014 02:58 PM, Richard Hipp wrote: > > > Under Admin/Access the "Public Pages" entry box allows you to specify > a comma-separated list of GLOB patterns for file that will be visible > to the public even if the source code access is turned off. This is > used, for example, to make the SQLite Encryption Extension > documentation files in the www/ directory visible > (http://www.sqlite.org/see/doc/trunk/www/readme.wiki) without making > the source code visible to non-licensees. > > 8080/cgi-bin/mailman/listinfo/fossil-users -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
