But I like Bert's solution-- and I think you can have it both ways, sorta.
His app_server is one file with the settings for all different servers.
Once the custom tag tells it which machine it's on, it executes the code for
that machine. In that sense app_server does something different for each
machine, even though it is the same file.
Really it is the same concept as using the index.cfm in Fusebox-- instead of
having main.cfm, add.cfm, delete.cfm, we have index.cfm?fa=main, etc... So
in app_server.cfm, we have a switch on the server name that runs the code
for each different server. If you wanted to have separate files, you could
take the next step and just cfinclude the settings for the different servers
in your switch in app_server, just like the fusebox index.cfm...
Ramble, ramble, ramble...
David Huyck
[EMAIL PROTECTED]
| Isn't the whole point of app_server that it's different on each server?
|
| -----Original Message-----
| From: Bert Dawson [mailto:[EMAIL PROTECTED]]
| Sent: April 11, 2001 8:20 AM
| To: Fusebox
| Subject: RE: Variable definition files
|
|
| Noam
|
| I think you may have missed the point: all the custom tag does is set a
| variable, request.thisserver, to the name of the box.
| Then in the app_server.cfm you do a cfswitch on the value of the variable.
| The advantage of this is that there is only _one_ app_server file - you
| don't have to keep them all in synch across the dev,test and live boxes
when
| you change something.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
