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
