In web2py we do not have the concept of a project. We have applications. Each application is a subfolder under applications. With other frameworks the concept of a project is needed because there is a single place where the project is configured (such as database uri). In the case of web2py there are no configuration files. Each app has its own models and they connect to the databases they need to connect to. Functionally you can say if two or more apps share the same DB, they are project.
You can use routes.py (as Yarko suggested) or apache virtualhosts (or both) to map URLs into the corresponding apps. The only reasons to ever have two distinct web2py installation are: 1) if you need two different web2py versions. Because of backward compatibility should never need it unless testing. 2) because you have different deployments (for example GAE deployments) that you want to keep separate. Massimo On Jan 16, 3:18 am, eka <ekagauranga...@gmail.com> wrote: > Hi all > > Wanted to give a try to web2py. I'm from linux world not a fan of > GUIs. > My question is... if I want to start a project named project1 web2py > is the root to my project? Since I saw that all apps are saved inside > web2py folder. > So if I have 2 projects should I have 2 web2py separate installations? > or? > > Regards
-- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
