(I'm copying the list, since I think you probably just forgot) On Thu, 2002-10-31 at 14:33, Gil Hauer wrote: > Hi Ian, > > I'm currently setting up environment to develop several applications in > parallel. These application are not related to each other so they'll be > living in completely separate workspaces. > > At this point I'm actually just setting up the revision control > mechanism so that more than one developer can work on the application at > a time. > > While MakeAppWorkDir is a great start for me it complicates the revision > control mechanism since I need to track two files that are effectively > the same (one in the original Webware directory and the other in the > WorkDir). > > Is there any reason why MakeAppWorkDir copies files rather than using > symbolic links? One of the advantages of the latter approach is that > when the Webware directory is updated to the next release the WorkDir > won't have to be modified ...
I think in most cases it makes small modifications. Symlinks also won't work on Windows. I think a better ambition would be to make those files thinner wrappers around the Webware equivalents -- AppServer could just call WebKit/AppServer, ditto AppServer.bat, NTService, Launch.py, and WebKit.cgi. Ideally then those files in your workdir will be so trivial they'll seldom change. > Also, to more directly answer your question: a cool feature to add to > MakeAppWorkDir is to also automatically update the httpd.conf file :) > That'll save a lot of guess-work and reduce the number of questions from > Webware neophytes like myself. Unfortunately there's a bunch of different ways you can integrate it into httpd.conf -- though maybe we could do something. Maybe have you put an Include statement in httpd.conf, and create a configuration fragment in the workdir. (Messing with the actual httpd.conf seems to hard). I'd be open to that -- maybe using mod_webkit or wkcgi, putting them in place, and supporting some basic mod_rewrite recipes. Ian ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
