At 06:35 27/09/2001 Thursday, you wrote: >Spike, > > wow... that sounds like an awful lot of messing about.
Yes, but then again, if it wasn't going to be a lot of messing about you probably wouldn't have had to ask the question in the first place :P > What about when >I need to work two modules together with a separate developer? And final >integration? How does that work? As long as you are always calling custom tags using cfmodule you can make sure that the only unstable modules any developer has are the ones he/she is working on themselves. As long as your developers are religious about tagging the stable versions of what they check-in it is fairly easy to make sure that this isn't an issue. If several developers are working on the same module then you pretty much have to accept the pain of merges and conflicts, but as long as the developers check in their changes regularly (like every 10 minutes) it isn't too much of an issue As far as final integration goes, you would probably be keeping CVS tags for the stable modules as they are built. The developers should always be using the latest stable version of any module so as to avoid any issues between modules. You can easily check-out the project from CVS and do a replace on #llistFirst(cgi.server_name)# and replace it with the static name of the mapping when you put it on the staging server. >The part about custom tags bothers me - I don't want to force the use of >cfmodule, but I rely heavily on custom tags which are shared throughout all >modules - and I'm constantly updating the things... I did have a few moral/religious problems with that at first, but after a while it came to be second nature to always use cfmodule for all custom tag calls in all applications Spectra or not. Having done things that way for a while I can't understand why I didn't do it a long time ago it gives you an enormous amount of power to control what is happening with your custom tags. For example, I often keep modules in a constant state of development and have a config file to indicate the directory containing the current version. As soon as a new version has been tested the config file can be updated with the new directory name. If there is a problem it is a 1 second fix to put everything back exactly as it was prior to the change. Try doing that with "CF_NewsItem" The cfmodule system also allows you to create entire applications which can be moved from 1 server to another and duplicated on the same server with only a change of a few entries in a config file while still allowing you to easily change any one of the copied modules to suit the specific needs of a project. I'm not sure if there are any performance problems with cfmodule, but I certainly haven't noticed them. >Thanks for the advice m8y, I'll probably continue to bug you about it <g> No problem Always happy to oblige a fellow sleep enthusiast >cheers, >Toby > >------------------------------------------------------------------------ > > Life is poetry, write it in your own words > >------------------------------------------------------------------------ > >Toby Tremayne >Architect / Developer >Code Poet and Zen Master of the Heavy Sleep >MercuryRed >Lvl 9, 123 Queen st >Melbourne >VIC 3000 >p: +61 3 9605 5035 >m: +61 416 048 090 >ICQ: 13107913 > >------------------------------------------------------------------------ >------------------------------------------------------------------------ >DISCLAIMER - All errors and omissions excepted. This message contains >privileged and confidential information intended only for the use of the >addressee named above. If you are not the intended recipient of this >message you are hereby notified that you must not disseminate, copy or >take any action in reliance on it. If you have received this message in >error, please notify Mercury Red immediately >----- Original Message ----- >From: spike <[EMAIL PROTECTED]> >To: Spectra-Talk <[EMAIL PROTECTED]> >Sent: Saturday, October 27, 2001 1:26 PM >Subject: Re: OT: Source Controlled Web Development - help needed > > > > Hi Toby, > > > > I have worked like this on a few projects. > > > > The basic setup we used was to have a separate website for each developer. > > In our case the webserver was IIS so it was a case of creating a directory > > to hold the application files for that user. > > > > To illustrate: > > > > suppose you have users: andy, spike, bob and fred. > > Your application is called spectrasite and can be reached at the domain > > spectrasite.com > > > > If you have control over DNS add entries for andy.spectrasite.com, > > spike.spectrasite.com, bob.spectrasite.com, bob.spectrasite.com and > > fred.spectrasite.com > > If you don't have control over DNS add these entries to the hosts files in > > each of the client machines and have them point to the IP Address of the > > spectra server. > > > > On the Spectra Server create a directory structure something like this: > > > > sites > > andy > > spectrasite > > wwwroot > > customtags > > includes > > plp > > rules > > sites > > spike > > spectrasite > > wwwroot > > customtags > > > > etc... > > > > For each of these directories create a web site which points to wwwroot >and > > another which maps the /allaire/spectra/ webserver mapping to the same >name > > on each of these sites on the server in order for the Designmode tools to > > work. The website which points to sites/spike/wwwoot/ should redirect > > requests for spike.spectrasite.com to that directory and the same should > > apply for each of the mapped developer names. > > > > Also on the spectra server add a ColdFusion Mapping for each of the > > developers: /andy/, /spike/, /bob/ etc. You may need to make these names > > different if you have a lot of developers, but the important thing is that > > they should map to the first part of the FQDN you specified either in DNS > > or in the hosts file. > > Each of these should point to the root directory of the same name. > > > > All custom tags must be called with cfmodule using the syntax: > > /#listfirst(cgi.servername,'.')#/spectrasite/customtags/tagname.cfm > > > > All PLPs, rules, handlers etc. should be called with the same syntax to > > make sure that each developer gets files from his/her own site. > > > > Now you have the ability for each developer to work independently of all > > the other developers for the application for a single install of Spectra >on > > the central server. Once code has been verified the developers can check >it > > out using the tool of your choice to their own directory on the server. > > > > When you decide to deploy you will probably want to update all the custom > > tag calls so that they aren't dynamic. > > > > We normally use CVS on Linux as the repository and WinCVS as the client > > > > Spike > > > > HTH > > > > At 04:53 27/09/2001 Thursday, you wrote: > > >Apologies for the OT post, but I really need some input here... > > > > > >We're trying to set up a new dev/staging/production environment with >source > > >control. One of our major problems / decisions is based aorund the > > >development cycle and how it works with source control. Obviously the >maxim > > >"work locally, store globally" is the perfect ideal. When you're talking > > >about something like C development this is simple - you just need a local > > >compiler. But we're running CF and Spectra, and several of the >developer's > > >boxes are not capable of running local copies of spectra. > > > > > >I don't want a situation where I have to check out a file locally, edit >it > > >blind, check it back in again, somehow move it to a browseable directory > > >then refresh the page and see my changes. When I'm trying to debug > > >something that's going to be a nightmare. Especially if we use CVS >instead > > >of MS Source Safe (and we'd prefer to implement CVS), because then we >have > > >an extra client to deal with, thus more alt tabbing all over the place. > > > > > >So I'm trying to work out the best solutions - how to handle the serving >of > > >these pages, where to check out to,(working directories) etc. Can anyone > > >lend some insight as to how their company does things, or how best they > > >might implement something? We can't do away with spectra as we have >several > > >large jobs requiring it, and we're pretty much stuck with not being able >to > > >run a local copy of spectra on everyone's box. > > > > > >any help at all would be appreciated... > > > > > >cheers > > >Toby > > > > > >------------------------------------------------------------------------ > > > > > > Life is poetry, write it in your own words > > > > > >------------------------------------------------------------------------ > > > > > >Toby Tremayne > > >Architect / Developer > > >Code Poet and Zen Master of the Heavy Sleep > > >MercuryRed > > >Lvl 9, 123 Queen st > > >Melbourne > > >VIC 3000 > > >p: +61 3 9605 5035 > > >m: +61 416 048 090 > > >ICQ: 13107913 > > > > > >------------------------------------------------------------------------ > > >------------------------------------------------------------------------ > > >DISCLAIMER - All errors and omissions excepted. This message contains > > >privileged and confidential information intended only for the use of the > > >addressee named above. If you are not the intended recipient of this > > >message you are hereby notified that you must not disseminate, copy or > > >take any action in reliance on it. If you have received this message in > > >error, please notify Mercury Red immediately > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
