As Matt says its fairly simple to create admin or per-app mappings to reuse the same copy of the frameworks across multiple apps.
However, just a word of caution; I tend to share frameworks amongst apps for the same domain/host/client, e.g msite.com/app1 and mysite.com/app2 would share the same ModelGlue & Coldspring codebase. For other clients/hosts/domains install a fresh copy of the frameworks, this way everything is pretty much self contained, and upgrades or patches to ModelGlue don't cause problems across all your sites. I think ModelGlue & Coldspring is < 10MB so its hardly worth worrying about Chris On 6 October 2011 22:27, Matt Quackenbush <[email protected]> wrote: > Yes. You can either have global mappings (e.g. in the CF Administrator) > for each framework or use per-application mappings for them in each > application's Application.cfc. > > Then you'd simply need to point the respective frameworks to each > site/application's specific configuration files (e.g. coldspring.xml, > modelglue.xml, transfer.xml, etc.). > > HTH > > > > On Thu, Oct 6, 2011 at 4:23 PM, marc <[email protected]> wrote: > >> I made a ModelGlue application and now I am making a 2nd application. >> Instead of installing a complete new instance of the ModelGlue framework for >> this 2nd application, could I use the same ModelGlue framework I installed >> for application1? >> >> My guess is yes: it involves creating Application-specific mappings for >> app 2 that point to the location of the MG framework I want to share. The >> only thing that should be specific to both applications is the ModelGlue.xml >> >> Is that correct? >> >> I also use Coldspring and Transfer. Could I re-use these frameworks as >> well in the same way - meaning I use App-specific mappings that point to >> Coldspring and Transfer ands have a Coldspring.xml and Transfer.xml for each >> application? >> >> I use ModelGlue 3.1.299, Transfer 1.1 and CS 1.2. >> >> Couldn't find this in the Quickdocs - sorry if I overlooked it and this is >> a RTFM issue... >> >> Marc >> >> -- >> Model-Glue Sites: >> Home Page: http://www.model-glue.com >> Documentation: http://docs.model-glue.com >> Bug Tracker: http://bugs.model-glue.com >> Blog: http://www.model-glue.com/blog >> >> You received this message because you are subscribed to the Google >> Groups "model-glue" 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/model-glue?hl=en > > > -- > Model-Glue Sites: > Home Page: http://www.model-glue.com > Documentation: http://docs.model-glue.com > Bug Tracker: http://bugs.model-glue.com > Blog: http://www.model-glue.com/blog > > You received this message because you are subscribed to the Google > Groups "model-glue" 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/model-glue?hl=en > -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en
