On Jun 19, 1:48 pm, David Marko <[email protected]> wrote: > I just decided today to explore the 'shell' function the web2py > browser interface offers. But I found it very unstable. This works > very fine until I want to get back to my app. It locks database access > that means entire web2py server is locked and must be killed. I know > the shell interface warns about this and lead me to click on > 'unlock ...' links, but it doesnt help. I have tried several times > with the same 'lock' end. My app is connected to PostgreSQL, I run > latest web2py trunk version on WinXP. The 'shell console' is very > powerful thing but useless when it causes server freeze. But maybe I > miss something significant. Can anyone share his experience or maybe > some hint?
hint is: "...it seemed like a good idea at the time...." (sqldesigner integration also falls in this bucket, I think) The command line shell is more powerful, and less problems --- and you can run it _while_ you are running the "other" server (which is, for example, how I would do custom reports from PyCon registration site - write a little one-shot function, and run it from a command line shell for someone, while the registration site was running on apache): python web2py.py -S myapp -M I have never found a situation where I couldn't get some ssh connection to my server to make this happen (putty, straight ssh, or otherwise), so the web shell was a curiousity... nice for demos, but not distinctly useful enough to bother with. That would be my best hint... - Yarko - Yarko > > David
