Bill,
Here are my Pros and Cons
Pointing each site to a separate directory and using a "shared_includes"
directory:
1.) I'd have to write the fusebox structure for every site.
2.) If I want to make global changes (like adding a fuse), I have to do it
to every site.
Pointing each site to the same directory:
1.) The app is exactly the same for all sites (except layout).
2.) I can add a fuse to the app and it affects all the sites.
3.) I can supply default (cookie cutter) headers and footers for users to
choose from. This will allow an entire site to be set up in minutes.
Here's how my directory structure will look:
/Inetpub
/wwwroot
/my-main-app.com
/content
/blocks
dsp_header.cfm
dsp_footer.cfm
dsp_Product_Results.cfm
/queries
qry_states.cfm
qry_Product_Results.cfm
/actions
act_Save_Product.cfm
act_Update_Product.cfm
/fred.com (In IIS, this points to
/inetpub/wwwroot/my-main-app.com/content)
/content
/blocks
dsp_header.cfm
dsp_footer.cfm
dsp_Product_Results.cfm
/barney.com (In IIS, this points to
/inetpub/wwwroot/my-main-app.com/content)
/content
/blocks
dsp_header.cfm
dsp_footer.cfm
dsp_Product_Results.cfm
The query in app_globals will tell me that fred.com and barney.com both use
custom dsp_ files.
So, in the my-main-app.com's app_globals, cfmap.blocks =
/fred.com/content/blocks OR cfmap.blocks = /barney.com/content/blocks
The query could also say that they use default header and footer files.
So, cfmap.blocks = /my-main-app.com/content/blocks
Brad
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 01, 2001 6:21 PM
> To: Fusebox
> Subject: RE: Reusing an entire fusebox app
>
>
> Seems to me like I would do this by managing the shared dsp, act, url, and
> qry files all in a "shared_includes" folder. Then each domain would point
> to its own index file within a real directory. Then create a
> mapping to the
> shared_includes folder called "shared_includes."
>
> Then each site could have its own Application file, app_locals, header,
> footer, etc.
>
> Each fuse in the circuit app would refer to the includes as follows:
>
> <cfcase fuseaction="NewUser">
> <cfinclude "/shared_includes/dsp_NewUserForm.cfm">
> </cfcase>
>
> Signed,
>
> Bill King
> HostWorks INC
> http://www.hostworks.com
>
>
>
>
> -----Original Message-----
> From: Brad Roberts [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 01, 2001 3:59 PM
> To: Fusebox
> Subject: Reusing an entire fusebox app
>
>
> I've created a fb site that I want to reuse for different domains
> (websites).
>
> I'd like some creative ideas on how to do it. Here's what I'm
> planning thus
> far:
>
> 1.) In IIS, point all the domains that share the app to it's root
> directory.
> 2.) In app_globals.cfm, query the db to get the sites info using
> cgi.server_name.
> <cfquery name="site" blah... cachedwithin="createtimespan(---)">
> select *
> from websites
> where domain_name = '#cgi.server_name#'
> </cfquery>
> 3.) Use the results from the query to set things like header and footer
> files, company info, etc.
>
> Is there any problem in doing it this way? I'd like some other
> solutions if
> anyone has any.
>
> Thanks in advance,
>
> Brad
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
