So I went with the module scenario, using only one application. The first module will be Billing. First model in there is Customer. Second model is Invoice.
How do I create a Billing module with Customer and Invoice CRUDs? Seems to me that I would have to create a Customer module and an Invoice module, which is not the structure I'm looking for. On Sep 20, 1:52 am, Magnus B <[email protected]> wrote: > This 2nd scenario is actually mine. CRM will talk to Billing, > inventory and probably all modules. > > If they're all in the same application, how do I structure things > within the modules? When I look at existing projects, they're almost > all some kind of CMS. There you'd have a frontend to show things to > users who read the blog / website and a backend for writing things. > Frontend and backend are completely different, but work towards the > same models. > > I feel like I'm wasting "structure" if I have One project >> One > application >> A few modules (CRM, Billing etc) and then tons of code > in each module. The average web site may not need more then one > application, but this is a "web application", it's not the average > CMS. > > Would the answer change if the individual parts of this application > only spoke to each other through and API, say a REST-based one? > > On Sep 19, 7:38 pm, Jake Barnes <[email protected]> wrote: > > > Will your CRM ever have to talk to Billing or Inventory? If yes, keep > > it to one application. If no, then I could see separate applications. > > > On Sep 19, 2:40 am, mbernasocchi <[email protected]> wrote: > > > > similar scenario: > > > > The application has several loosely tied parts that can be used > > > separately or together, and all share the same login. > > > > Think ERP here, with CRM, Billing, Inventory etc. All parts are > > > modular within the main application, but they are all pretty big > > > applications with many modules themselves. > > > > I figure there's three options: > > > > 1. Each part is its own project. > > > 2. One project, each part is an application within. > > > 3. One project, one application, each part is a module within. > > > > #1 feels to strict, no tie between the parts. > > > #2 feels great, I'm just not sure how it will actually work within > > > Symfony. > > > #3 feels like trying to fit an application within the frame of a CMS. > > > > I want to go with #2, I just want to assure myself that I won't shoot > > > me in the foot doing so. Razz > > > > What do you guys think about it? > > > > On Sep 18, 7:46 pm, Sid Bachtiar <[email protected]> wrote: > > > > > Modules because I think basically if two things share users, they > > > > should be in the same apps as modules. > > > > > On Fri, Sep 18, 2009 at 11:42 PM, Gareth McCumskey > > > > <[email protected]> wrote: > > > > > In my opinion .... same project seperate modules. Getting two seperate > > > > > applications to talk can sometimes be tricky > > > > > > On Fri, Sep 18, 2009 at 1:09 PM,mbernasocchi<[email protected]> > > > > > wrote: > > > > > >> Hi, I'm starting a new (my first with symfony) project which has a > > > > >> forum and a blog. I'd like to have a static home page that links to > > > > >> the two and to have cross links between blog and forum. > > > > >> Is it better to create a frontend app with forum and blog modules or > > > > >> to create two different applications? And why? for the backend i'll > > > > >> create a different app. > > > > > >> thanks a lot > > > > >> Marco > > > > > > -- > > > > > Gareth McCumskey > > > > >http://garethmccumskey.blogspot.com > > > > > twitter: @garethmcc > > > > > -- > > > > Blue Horn Ltd - System Developmenthttp://bluehorn.co.nz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
