I missed the part about verification. That's probably the issue. On Tue, Jan 4, 2011 at 11:56 AM, mdipierro <mdipie...@cs.depaul.edu> wrote:
> Oops. I missed a file in the commit. adding it now. > > One more caveat. For security, the first user is the teacher and > registration is enabled by default. > For all other users of admin (students) registration requires > verification. That means the teacher must login, user /admin/appadmin > and clear the content of the "registration_key" field for approved > students. > > This is for preventing non-students from getting their hands on the > system. > > Massimo > > On Jan 4, 10:44 am, David Bain <pigeonfli...@gmail.com> wrote: > > Massimo, > > Nice! It works... so as long as I register first I'm the teacher :). > > I'm just looking at web2py again in the last few weeks. I'm very happy to > > help with documentation of this feature. Just point me in the right > > direction. > > > > see: Screenshot below: > > [image: user login.jpg] > > > > On Tue, Jan 4, 2011 at 10:54 AM, David Bain <pigeonfli...@gmail.com> > wrote: > > > Thanks Massimo, > > > Checking out trunk now. > > > > > On Tue, Jan 4, 2011 at 10:49 AM, mdipierro <mdipie...@cs.depaul.edu > >wrote: > > > > >> In trunk. > > > > >> - Deploy the latest admin > > >> - edit file applications/admin/models/0.py and set > > >> MULTI_USER_MODE = True > > >> - Try access admin and it will require registration/login > > >> - The first user to register is teacher (can see all apps) > > >> - All other users are students (can only see/edit/create their own > > >> apps) > > > > >> This does not prevent one user from writing dangerous code. The code, > > >> whoever creates it, always runs under the same privileged and has > > >> access to the entire web2py folder. > > > > >> At the moment students get access to each other appdmin controllers. > > > > >> Please help with testing! > > > > >> On Jan 4, 8:28 am, David Bain <pigeonfli...@gmail.com> wrote: > > >> > I like the modified admin approach, it would be simpler, for > teaching > > >> > purposes it would work, it would need to be modified for production > > >> style > > >> > scenarios as it would not be an acceptable risk. > > > > >> > On Tue, Jan 4, 2011 at 6:50 AM, mdipierro <mdipie...@cs.depaul.edu> > > >> wrote: > > >> > > This can be done but it would not prevent one use to write code > (an > > >> > > app) that reads or deletes another user app. As long as this is > clear, > > >> > > I coud modify admin for this purpose (or create another admin). > > > > >> > > On Jan 3, 10:13 pm, VP <vtp2...@gmail.com> wrote: > > >> > > > I think it'll be convenient for multiple users to work on one > web2py > > >> > > > installation, if there's a layer on top of the admin app, > providing > > >> > > > the following features: > > > > >> > > > 1. The admin app allows user registration. > > >> > > > 2. Each user can view/edit only apps that he/she creates. > > > > >> > > > This is strictly at the (admin) app level. Everything is the > same > > >> as > > >> > > > before at the filesystem level. > > > > >> > > > (This is particularly useful for teaching (I think): one web2py > app, > > >> > > > many students). > > > > > > > > user login.jpg > > 41KViewDownload >
