***************************************************************************
*** 		README for Bayfield County GIS App Code			***
***		Version 1.0						***
***		02/24/2009						***
***		Administrative contact: Scott Galetka			***
***			(715) 373-6156					***
***			sgaletka@bayfieldcounty.org			***
***		Technical contact: A.J. Van Beest			***
***			(715) 373-6319; skype: ajvanbeest		***
***			ajvanbeest@bayfieldcounty.org			***
***			yahoo: theaj42; gtalk: ajvanbeest		***
***************************************************************************

1. What's included in the zip
	A. Folders
		1. Webpages
			a. CGI-BIN			// a repository for cgi scripts
			b. LandRecords			// the html for the Bayfield County Land Records web presence
			c. cgi-bin2			// another repository for cgi scripts
			d. Ortho			// orthophotography images, a couple apps, and at least one cgi script
			e. Proj				// ???
			f. viewer_images		// basic MapViewer application icons, etc.
		2. Apache-Conf
			a. httpd.conf			// our basic Apache (2.2.x) configuration file
			b. httpd-vhosts.conf		// more specific Apache configuration information
			
	B. A Note - So these are our actual files from our actual servers. By giving you this information, we've
	made it really easy for you to be mean to us. But hey, you want our money, not our ire, so here's a
	completely unenforcable agreement which nonetheless makes us feel better about things: By unziping this 
	document and looking at the files therin, you forsake all nefarious purposes (in regards to Bayfield
	County and this project; what you do on your own time is your own business) and just put on your
	"helping hat." And maybe a toga.
			
2. Bayfield County web server setup
	A. Then - We ran everything as mostly-static (ASP used pretty much only for server-side includes) pages
	being served via IIS 6 hosted on Windows Server 2003. The County GIS application was built on MapServer 
	(http://mapserver.org/) and maintained by a consultant who did a good job. The GIS apps were the sole exception 
	to the static pages on the site. It was dynamic, and seemingly based on classic ASP and some cgi. 
	Everything ran well, children played in the streets, and our kingdom was at peace.
	
	B. Now - We're running a WAMP stack (still w2k3, Apache 2.2.x, MySQL 5.x, PHP 5.x) to host a content
	management system. The GIS application that was written specifically for IIS and CGI still lives on IIS (on 
	port 8080). In a perfect world, the httpd-vhosts.conf file would direct traffic for the CMS to Apache (on 
	port 80) and traffic for the GIS app to IIS at *:8080, then upon sending the requested http data, rewrite
	the outgoing URLs so everything looks like it's being served seamlessly from "bayfieldcounty.org." In reality,
	this works for users inside the domain, but not for users from the WAN, who tend to have the GIS app hang before
	it finishes loading. Dark clouds have gathered over our kingdom, and legions of frustrated users are marching
	on our gates.
		
3. What we need
	A. Our perfect solution looks something like this: We serve great (detailed, useful, understandable, flexible) 
	GIS information to our users either from "bayfieldcounty.org/*" or from "*.bayfieldcounty.org." If you host our 
	GIS apps, your price is reasonable, your tech support is useful and approachable, and your backbone connection 
	is blazing-fast. If we host our GIS apps, things play well with our current WAMP stack (and we're open to 
	modifying that stack, as long as the changes don't poke a stick in the eye of our CMS), your price is still 
	reasonable, your tech support is still superb, and we'll live with our pipe. And oh, by the way, our CMS 
	takes care of the rest of our web universe (and you can ignore this; we've [more-or-less] got it). Our skies 
	are again clear, our gates are wide open, and our children are happily muddy.