[Moin-user] will moin-moin be adapted to my needs? (corporate wiki)

[Yusuf Abdulghani]

Oliver,

All that you mention can be done very easily with MoinMoin wiki and all 
of them in one wiki. Use groups to group your users for access to 
specific parts of your wiki. I would highly recommend that you use 
"templates" with predefined ACLs to create pages so that your users do 
not mess up the permissions and mistakenly allow others (or people from 
other companies) to read your pages.

The default permissions for each page will be set so read/write/admin 
for the AdminGroup. For the rest of the users (Known/All), set it such 
that no one can read any pages. Divide users into groups. Create a 
"homepage" for each client and give read access to that page only to 
the group(s) of users who should see it. On that "homepage", give the 
users a button to create subpages (using "NewPage" macro) based on 
templates whose ACLs are already set. This will ensure that your users 
don't have to worry about ACLs.

I have found MoinMoin to be very easy to use and maintain (especially 
after the 1.3.x release). The interface is clean.

Hope this helps.

Yusuf

On Mar 2, 2005, at 11:05 AM, Olivier Mueller wrote:

> Hello,
>
> I'm currently navigating across http://c2.com/cgi/wiki?WikiChoicetree
> trying to find the "perfect" wiki, and it seems that moinmoin is
> the one: well designed, python, file upload support, simple, ACL's.
>
> Here is what I'd like to have: if you have a few seconds, I'd be
> happy if you could tell me if it could be done with moinmoin.
> (I plan to play with moinmoin's ACL later today).
>
> Goal would be a kind of "corporate" wiki, with a public part
> for public projects (open source), and different private parts,
> for server documentation:
>
> /Public/PublicDocument1   -> rw access for everybody
> /Public/PublicDocument2   -> rw access for everybody
>
> /Customer1   -> private, rw access for UserA, UserB, UserC
> /Customer2   -> private, rw access for UserA, UserD, UserE
>
>
> UserD should only be able to see the Public part and
> the documents in the /Customer2 tree, and he shouldn't
> even see that there is a "/Customer1" tree:  is that
> possible, or would it be to unsecure?
>
> If necessary I could setup one standalone wiki per
> customer or project, but I guess it would be nicer
> with just one... :)
>
>
> About security, I'd like to use the wiki to store
> some sensitive passwords (each of these "customers" have servers):
> how would you do that?   I'm thinking about using
> a kind of "gpg" pad, and store only some blocks like
> "gqQXy5kJIlB4sGxJE+u0DbvPdX5U2mLFMxULL2kK0YIpOU734EywLi65XxHEKlXV
>  sOOyskZs/BjIJmWoBsOMIujUMbMYlk4UoSSLyP8zJyuRwCob41zhed2CMG3CTLXE"
>
> To get the cleartext data, the user should than copy paste
> these line somewhere and give in the "secret" key (not stored on the
> wiki). Does it sound ok?  Maybe there are even modules/macros for
> that, I'll search... :)
>
>
> Regards,
> Olivier
>
> -- 
> _______________________________________________________
>  Olivier Müller - PGP key ID: 0x0E84D2EA - Switzerland
>     E-Mail: http://omx.ch/mail/ - AIM/iChat: swix3k
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Moin-user mailing list
> Moin-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/moin-user