Ok, what I did was this: Ran the app through CF_2CFModule Edited the Environment.cfm file to reflect the paths etc. at the Hosted site Uploaded the whole mess to the host Tried to run setup.cfm and got many errors, including that the mapping may not be correct. Here's the thing... on my dev box, I have a mapping of /cghomes which points to a virtual directory. On my host, the mapping _should_ be the root of the site, no? If so, how do I set that in Environment.cfm?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Churvis Sent: Monday, March 28, 2005 4:06 PM To: [email protected] Subject: Re: [plum] Production Help > In my development application, I have a virtual directory of /cghomes, where > my app lives. This is also the CF Mapping. So http://localhost/cghomes shows > me what I want. Obviously, I am missing something easy, because I do not > want my production site to be at a subdirectory. However, I can't set the CF > mapping to "/" in the Plum IDE > The Plum Help mentions setup/staging and setup/production folders, each with > their own environment.cfm file, but I am not seeing these. Further, how > should I be setting up the mapping at my host? I am a bit confused. I must > be missing something simple, but it's Monday, and I just can't get this > thing to work. Your development, staging, and production sites will be on your development, staging, and production servers, respectively. Each of these servers is a different machine, so each one may (and most likely will) have different values for things like disk paths, URLs, etc, which is handled by each server's own version of Environment.cfm, each server's own mappings, etc. So you develop your Plum application on your development server, test it as best you can as the developer, then migrate it (either through copying or via source control, which is the preferred method) to your staging server where people who are not as close to the application as you are will test it outside of your "box," which will uncover problems you wouldn't normally think about. Once you're done with the staging-bug fix cycles and the QA crew who has been testing your site on the staging server gives it the OK, you migrate the application to your production server, which will also have its own Environment.cfm. If your production server is in a shared hosting environment, you will want to test on each server using a copy of the application that has been run through CF_2CFMODULE. I hope this helps. Respectfully, Adam Phillip Churvis Member of Team Macromedia http://www.ProductivityEnhancement.com Download Plum and other cool development tools, and get advanced intensive Master-level training: * C# & ASP.NET for ColdFusion Developers * ColdFusion MX Master Class * Advanced Development with CFMX and SQL Server 2000 ********************************************************************** You can subscribe to and unsubscribe from lists, and you can change your subscriptions between normal and digest modes here: http://www.productivityenhancement.com/support/DiscussionListsForm.cfm ********************************************************************** ********************************************************************** You can subscribe to and unsubscribe from lists, and you can change your subscriptions between normal and digest modes here: http://www.productivityenhancement.com/support/DiscussionListsForm.cfm **********************************************************************
