On Thu, 10 Oct 2013 20:24:35 +0200, Richard Hipp <d...@sqlite.org> wrote:

On Thu, Oct 10, 2013 at 2:19 PM, j. van den hoff
<veedeeh...@googlemail.com>wrote:


thanks for clarification. another question which comes up for me for the
first time: it seems that either all wiki pages are viewable w/o login or
none at all. i.e. there is no finer-grained access control (e.g. on a
per-wiki page basis). is this right? while access-control on a per-page
basis might be overkill it would be rather nice to have a distinct
landing/welcome page which could be _always_ world-viewable while all the confidental content (in case there is such content) could go to other wiki
pages.

is there a way to achieve this or might this be a useful feature?


Under Admin/Access there is an entry box marked "Public Pages" that gives
public access to an otherwise locked-down Fossil site, based on glob
patterns.

I'm not able to make this work. my specific need would be to just give `nobody' and `anonymous' (i.e. everybody not explicitly authorized) essentially no capabilities _except_ viewing the landing page, i.e. `/home'.

first problem: if I remove _all_ capabilities for, e.g. `nobody', the web gui always asks for login when trying to navigate to the repository URL. so I'm not able to go to the home page at all.

question 1: which capabilities should I set for these users (`j' seemingly grants access to all wiki pages and every other capability I do not want `nobody' to possess)?

question 2: what specifically have I do put into "Public Pages" in order to restrict viewing to `/home'?

question 3: what is the adequate setting for the default capabilities (usually "u") on the same page and how does it interfere with the above?

if all this is documented somewhere please give me a tip.

thanks
j.





--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to