also look into scripts/tickets2db.py On Jan 21, 10:34 am, Jeff Bauer <[email protected]> wrote: > That shouldn't be too hard to do. In the meantime, I > realized that I could just grab the tickets from: > > web2py/applications/myapp/errors > > Jeff Bauer > Rubicon, Inc. > > On 01/21/2010 08:12 AM, mdipierro wrote: > > > It should be trivial to make a view_tickets app by taking the > > appropriate action from admin and add auth. > > > I encourage people to build one and I will be happy to post it. > > > Massimo > > > On Jan 21, 7:51 am, Jeff Bauer<[email protected]> wrote: > >> 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 [email protected] > >> - 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
