>
> 1. Is it advisable to define each of my 'models' as separate applications
> or to incorporate them all into one (my instinct would be to have them
> separate as their respective functionality is separate).
>
if you have same define tables for every app, i think, it's better to
define it on modules, becase it can be used by another web2py app.
>
> 2. My project will consist of multiple applications (at least 2 but
> depends on answer to 1st question). It seems that every application
> defines it own database. How do I specify I want every application to use
> the same database? In particular, I only require one set of auth files.
>
i think it just DAL constructor, you just need to set it in both apps that
refer to only 1 database on each web2py app.
>
> 3. The menu items will mainly be the same irrespective of which part of
> the site you are on (e.g. public links, wiki links, member links) - what is
> the best way to get the respective menu.py modules to generate the menu
> items?
>
what do u mean irrespective, for menu i think you can combine it with rbac.
e.g.
*models/menu.py*
if auth.has_membership(role = 'public'):
response.menu += []
if auth.has_membership(role = 'member'):
response.menu += []
*controllers/public.py*
auth.requires(auth.has_membership(role = 'public'))(lambda: None)()
best regards,
stifan
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
