iis - Multi-application Coldfusion 7 server and CFC paths -

iis - Multi-application Coldfusion 7 server and CFC paths -

we have coldfusion server hosts multiple applications, in own subfolder. like:

/webrootfolder/applicationa /webrootfolder/applicationb

furthermore, on development server, have re-create of given application per developer, each beingness subversion working copy:

/webrootfolder/applicationa_dev1 /webrootfolder/applicationa_dev2 /webrootfolder/applicationa_dev3

since running coldfusion 7 (with major resistance upgrading), find myself stuck want utilize cfcs in packages. here various issues, attempted solutions , issues these too:

using relative component name works if there single package, create mess of components in single folder. using sub-packages works long never reference components in parent packages, seems happen when extending, instanciating or using component cfargument type. using total chlorofluorocarbon path starting root doesn't work our multiple copies per developer. ** using dynamic path variable solution of now... until realized doesn't work extends or cfargument type... ** using server mappings doesn't work in development have 1 alias per developer copy. expect code folder-independant. ** using application specific mappings (defined in application.cfc) doesn't work because cf7 , not cf8+. creating local dummy copies of needed cfcs , cfinclude-ing content of actual cfcs (with relative paths "../../") previous solution. works, it's messy having these clones over. ** recently, have discovered solution not work. coldfusion gets confused same-named functions beingness included in various cfcs apparently. using development coldfusion servers on each developer's machine, allowing application path /webrootfolder/applicationa (suggested mark kruger). ** main issue here convince computer team allow install this. might take long time, fear don't have. ** there may other issues network configuration (giving access db maybe, i'm not sure) have go through network team , take while, if it's allowed. one website per application / folder - changing root

i have taken time explore way websites/applications configured in iis 6. after research, found out it's possible create bindings used under unix/apache. @ moment, applications in own subfolder of web root. aliases configured, making "domain.com/appa" point "/webrootfolder/applicationa" folder, example. still single iis website lots of sub paths. coldfusion root (for chlorofluorocarbon , includes) based on root of 1 website (/webrootfolder).

i made quick test , managed have sec iis website on server, bound port 8080 (instead of default 80). made 1 point straight /webrootfolder/applicationa/cfm (which root of app). this, coldfusion recognizes folder root , instanciating "object" chlorofluorocarbon looks /webrootfolder/applicationa/cfm/object.cfc.

this had in previous job , worked well. said, little company , fear solution may have issues. mostly: how point people website? using port binding isn't user friendly (our users not techies). having specific domain each application sounds nice might costly, if https involved (or i've heard). subdomains might solution seems have similar issues.

so...

have missed anything? stuck 1 of "messy" solutions?

i have access coldfusion admin panel , perchance iis configuration, though i'll limited if solution affects paths or urls of other applications on server.

i 1 time asked directions fishing lake old farmer in southern illinois. scratched head moment , said me, "son, can't there here." :) think may in same boat leo.

the problem not packaging, problem sdlc goes against best practice. sort of "dev" server should mirror production - have scrambled approach. moreover, appears developers each have copy of own code on dev server. makes me think 12 years when buddy , i, starting our little dev shop, hosted code on dev server , developed against straight - approach not sustained , larger team worse gets have found.

what should run dev server mirror of production. allow developers run code on own workstations - local development phone call it. utilize source command handle differences, merging branches etc. in case each of developers utilize packaging intend , these sort of issues go wayside.

i realize i'm giving solution "cuts gordian knot" speak - right one. imagine wasting effort , time current configuration , suspect production deployments or assembling code qa huge challenge @ moment.

iis coldfusion iis-6 cfc coldfusion-7