Right. Then why does the whole ticketting system depend on "admin" ?
It is even said in the Deployment Recipe chapter of the doc <http://www.web2py.com/books/default/chapter/29/13/deployment-recipes#Collecting-tickets> : "You can later view the errors *using the admin app*, clicking on the "switch to: db" button at the top, with the same exact functionality as if they were stored on the file system." Same goes for appadmin.py and its permission-based "manage" feature which is described as a role-based database access. Why would you define roles in a local environment ? Obviously this is meant to go on production in a secure back-office... Admin is designed as more than a testing tool for a local or development environment, yet it is not meant to be deployed on production. I now get why many blogs and forums discussing "web2py vs other framework" always end up mentionning that developping on web2py starts as a very thrilling experience but often leaves a bitter taste. On Wednesday, November 26, 2014 8:48:49 PM UTC+1, Niphlod wrote: > > I agree, but let us remind that the "admin" app is not meant to be > deployed anywhere in production: its probably the reason why the > "corner-case" surfaced now instead of some time ago. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
