I do not really want authetication. The app will be accessed locally but on network drive. I want to do it as simple as possible for the user.
So the user just runs a command from terminal and the app opens i firefox. When he closes the app this will close the app. But can you store a sqlite db in sthe session? Den tisdagen den 19:e juni 2012 kl. 17:51:47 UTC+2 skrev Massimo Di Pierro: > > If the app is not the network you need authentication. In this case > youneed a shared persistant databases. > > Why not store everything else in session and do a session cleanup on login > and logout. > > massimo > > > > > On Tuesday, 19 June 2012 10:04:08 UTC-5, glomde wrote: >> >> In my case I would like all my data to be lost when the app is closed. But >> I assume one could think that the user saves the data as well. >> >> The app is not very complicated, but I want to have a GUI interface. >> What the app should do is to read a file that the user chooses. >> This will the generate a DB. From the DB the user can generate >> reports that are possible to browse and to filter on different values. >> >> I would like to use web2py instead of a GUI application for several >> reasons. >> Main reason is to only depend on python. Most python gui bindings you need >> to have the some gui backend installed. >> >> There will not be concurrent users. But the app will be on the network and >> several user can start the app at the same time. >> >> I also assume that some user would like to open several files. That is to >> have more that one session open. But in general I just want the user to >> open >> the app and easily close it. That is not to explicitly have to shut down >> the server. >> >> >> Den tisdagen den 19:e juni 2012 kl. 16:22:35 UTC+2 skrev Massimo Di >> Pierro: >>> >>> 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 >>>> >>>> >>>> >>>> >>>> >>> >>>
