I'm using web2app for a small one-off application in a corporate setting, quickly making changes to code to get a project done. Two users behind a corporate firewall. It's become a real hassle when application errors occur because the tickets aren't visible.
I can understand not making the admin interface accessible over an insecure connection, but because the ticket notification is tied to the admin system, here's what I have to do: - user reports an error, sends me the ticket - I fire up another copy of web2py on a different port - run a proxy: ssh -L 8001:127.0.0.1:8001 m...@192.168.2.56 - get the ticket info - shut everything down That's a lot of work just to get a traceback when attempting rapid development. There are settings where read-only access to the ticket info is justified, even if you don't want to grant users full admin access. -- Jeff Bauer Rubicon, Inc.
-- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
