I would add the normal setup is not only easier but also in this case more 
secure because replacing the data will create major security issues. If the 
data is in a single place you can use web2py's access control mechanism to 
make sure users can only access what they have permission to access and no 
more.

On Monday, 30 July 2012 11:42:20 UTC-5, Niphlod wrote:
>
> there should be only one instance of web2py active (e.g. on your 
> computer). All other labs should be able to reach your computer via browser 
> (so probably you'd have to configure the firewall if something goes wrong).
>
> You should start web2py with the -i parameter set to 0.0.0.0 (or insert 
> 0.0.0.0 instead of 127.0.0.1 inside the default widget) to allow web2py to 
> "respond" to calls done by other computers in the net targeting your 
> computer.
>
> If this is possible (i.e. other labs share the same network and your pc is 
> reachable by them) the app will be available for others using their 
> browsers just opening 
> http://your_pc_ip:8000/yourappname/yourcontroller/yourfunction.
>
> If this kind of setup is a no-go (i.e. very strict firewall rules) than 
> you should code your app wisingly with a shared database: if multiple 
> instances (i.e. one-per-lab) are active one instance could block the other 
> if you're using sqlite, and there are race conditions to consider (e.g. 
> lab1 loads the 3rd row of a table to edit that, while lab2 saves the 3rd 
> row - would win the subsequent save of lab1 or should the value saved by 
> lab2 be the "winner" ?)
>
> There are ways to mitigate that in web2py: let's not go deeper into that 
> if the "normal" setup is going to work (one web2py instance, lab2 
> connecting with the browser to your single instance)
>
> Il giorno lunedì 30 luglio 2012 09:36:32 UTC+2, Seelife ha scritto:
>>
>> Hi Folks, I am very new to web2py and my programming is wayyy behind.
>> However, I have built a very simple app for our laboratory to store 
>> data.  We have a number of different sites and I wouyld like the other 
>> users to access and use the app to input data as well.  The problem is, we 
>> work within a healthcare system so do not have access to the hospital 
>> servers and for reasons of data security, cannot store data offsite on a 
>> hosted server. So, I cant place the app on any other apache server etc.
>> At present, I have built the system on one of the "shared disks" 
>> available to lab workers.
>> Now, as web2py admin, I can navigate on my desktop to the shared disk, 
>> start the web2py roocket webserver and run my app.
>> But what is the process to provide access to the app for users elsewhere 
>> - they can also access the shared disk.
>> Is there a shortcut I can create that opens the app or do they also have 
>> to start the webserver?
>> Sorry for the basic question, can someone please give me a simple 
>> overview on how to set this up.
>> Thanks and regards  
>>
>>

-- 



Reply via email to