> 1) How I can extend standard `auth` table to store more fields (phone, > money, etc,). Should I create new table with all that data and link it > to original auth table or alter auth class to store all that data.
Here's the link to the section on customizing auth in the web2py book: http://www.web2py.com/book/default/chapter/08#Customizing-Auth > 2) Is it necessary to create different applications: (Profile, > Finance, Fickets, SMS, etc) to handle this requests: > /profile/changepassword, /finace/getlast10payments, /tickets/add, /sms/ > exporttocsv… > or I can work within one application and use some kind of url-mapping > to map /controller/function to /application/controller/function calls ... same here: http://www.web2py.com/book/default/chapter/04#URL-Rewrite > 3) If i chose mult-application way. How i could share desing/menu/ > session within applications I wouldn't go that way, instead of an application, create a controller for each cluster of functions. By the way, Auth implements functions to change your password etc., why not use them instead of implementing your own controller? Kind regards, Annet.
