Hi Richard, Thank you for the advice. I hadn't yet looked into web2py plugins and now that I read carefully the docs it seems that it can be a great solution!
What I am worried about is that I see my models grow rapidly and I read somewhere (I can't find the post anymore) that models should be kept small because there are executed on each request. Plugins seem great but do they really help in keeping these "*models accesses*" low? I might want to try optimise too soon (this is my first real app with web2py) and maybe it is fine that for example " *pluggin_blog.py*" model is accessed on each request although the client doesn't hit the page ever. Am I right? thanks for the help On Monday, 13 April 2015 15:29:51 UTC+2, Richard wrote: > > If it all for the same client, I would say single app... Think : db > backup, one app will growth faster than the other, more boiler plate (2X, > or more if you have more than 2 apps), all the issues you already aware of > regarding authentification... > > I would suggest you to use web2py plugin system if you want to reuse app > component in different app, so you keep everything in the same project but > you "modulized" them as plugins... > > Richard > > On Fri, Apr 10, 2015 at 8:19 AM, Sébastien Loix <seb...@gmail.com > <javascript:>> wrote: > >> Hi to all, >> >> I would like to ask for some advices on my web2py application >> arquitecture as I am seeing it grow rapidly and it might be a good time to >> start thinking it through before it is too late :) >> >> The website I am working on consist of several big parts (for now it has >> 2 web2py applications): >> >> + Events (*almost done*) : *App 1* >> + Shop (*almost done*) : *App 1* >> + Blog (*not yet developed*) >> + Content Management for the above (*almost done*)* App 2* (it has its >> own users and thus a separate auth_user table) >> + User Profiles (small social network with user timeline) (*not yet >> developed*) >> + Control Panel (stats, user management, logs...) (*not yet developed*) >> (will probably go inside App2) >> >> They both share the same models (except the auth_user tables) and >> database, with *App 2* being the one with migration turned on. >> I have so far *73 tables* and I will probably need some more for things >> like "comments" or "likes". >> >> As I still need to build 2 big sections (a blog and user profile with >> content generated) I am wondering what approach would be the best: >> >> - Create 2 separate applications with their own databases. I wonder >> then if I will have issues with user authentifiaction between those apps >> (I >> read here https://groups.google.com/forum/#!topic/web2py/e15Q0SYjX_w that >> there shouldn't be any problem though) >> - Start using some conditional models (I have* lazy tables* turned on >> and I read somewhere that conditional models aren't really that useful >> anymore?) >> - Keep Start using modules and import models from there (never done >> it, I might need some advice). >> >> For the info I am deploying on GAE with Cloud SQL (MySQL). >> >> Thanks for any advice and help on this, greatly appreciated. >> If anyone has successfully developed a website integrating several web2py >> apps I would love to hear from it. >> >> Cheers!! >> >> -- >> 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+un...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
