Here are my needs. example.com = public portion of the website. This includes anything publicly accessible, and allows new accounts to be created. Only needs access to one table, accounts table. dashboard.example.com = internal portion of the website, which includes all account management functions, but of course linked to the same database, but has access to many more tables.
In this setup, I would run two apache virtualhosts, and two installations of web2py. I will define my models in a module that they can be imported to each app. Each app will of course have a different set of controllers/views/static etc etc. And dashboard.example.com will be force https, IP restricted (by apache), htpasswd, web2py passwd, etc.. etc.. Is this an appropriate setup for this? Would having one app that checks request.env.http_host and route based on this a better solution? What would be the correct way to design the models so they can be imported instead of "exectued", like Admin but I need them to unpack into the web2py global namespace. Since I am on linux, would symlinks be a better approach I could store just the accounts table in one file, and symlink that to both apps from a central "projects" folder. Thoughts, suggestions, ideas? -Thadeus -- 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.
