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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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). > >
