Are you saying all your data should be lost when the app is "closed"? Can you tell us more about the use case? Are you going to have concurrent users at all? Should they share any data? Do they need access to admin at all or just appadmin?
On Tuesday, 19 June 2012 04:58:24 UTC-5, glomde wrote: > > Hi, > > I was thinking of using web2py as standalone desktop application. > After some tinkering I realized I needed to resolve some things. > > What I want > * Application should be completely standalone. Each start of application > should have its own DB. > * When user starts app, browser should open with the app, without asking > about admin password. > * App/Server should shut down when no pages of app is open. > > So I thought to create a init app as descripted by > > http://web2py.com/books/default/chapter/29/14#How-to-distribute-your-applications-as-binaries > > This solves some parts but I have some more things that need to be fixed: > > * How to make so that app starts without asking for admin password. > * How to start app on unique port that is not used. > * How to have seperate DB for each instance. I thought of using sqlite in > memory to make the instances independent of each other. Would this work? > * I would like a instance to quit when not used anymore. I thought it > would be possible if each page with ajax > requires updates. If no updates asked for X minutes, I would now that > there are no pages open and the server could > shut down. How to implement this? > > > BR, > > Toni > > > > >
