RE: Virtual Directories for Websites...follow-up remarks
Ok...I've answered my own question with more experimentation... If I used an established site, then I can created virtual directories for development and point clients to http://www.development.com/clientsite/index.cfm Rick -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:07 PM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195209 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
I'd recommended removing the cfdocs directory completely. The documentation is available at livedocs.macromedia.com or from within HomeSite or Dreamweaver. It can also be downloaded from www.macromedia.com. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:07 PM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195216 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Virtual Directories for Websites...follow-up remarks
You can also use different port numbers. >Ok...I've answered my own question with more experimentation... > >If I used an established site, then I can created virtual directories >for development and point clients to >http://www.development.com/clientsite/index.cfm > >Rick > > > >-Original Message- >From: Rick Faircloth [mailto:[EMAIL PROTECTED] >Sent: Thursday, February 17, 2005 12:07 PM >To: CF-Talk >Subject: Virtual Directories for Websites...follow-up remarks > > >Ok...I see that Virtual Directories work just like I thought they should >for websites that have domains pointing to the server already. > >However, I usually show my clients their websites as they're being >developed by using a direct URL, such as >http://66.xx.xx.138/cfdocs/website/index.cfm. > >That keeps it out of the public eye, yet gives the client access during >the development process. > >Is there a way to do the same thing if I'm using directories not under the >wwwroot? > >Perhaps, a main website with virtual subdirectories for the sites under >development, >such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? > >I'll try that... > >Rick > > > >-- >No virus found in this outgoing message. >Checked by AVG Anti-Virus. >Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195219 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Is there any particular reason for removing the cfdocs directory? Space? Any possible complications from not having anything that's in there? Rick -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:24 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks I'd recommended removing the cfdocs directory completely. The documentation is available at livedocs.macromedia.com or from within HomeSite or Dreamweaver. It can also be downloaded from www.macromedia.com. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:07 PM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195221 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
You mean a different port number for each site under development? e.g http://66.79.46.138:85/DevelopmentSite/Index.cfm ? Rick -Original Message- From: Kwang Suh [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 11:35 AM To: CF-Talk Subject: Re: Virtual Directories for Websites...follow-up remarks You can also use different port numbers. >Ok...I've answered my own question with more experimentation... > >If I used an established site, then I can created virtual directories >for development and point clients to >http://www.development.com/clientsite/index.cfm > >Rick > > > >-Original Message- >From: Rick Faircloth [mailto:[EMAIL PROTECTED] >Sent: Thursday, February 17, 2005 12:07 PM >To: CF-Talk >Subject: Virtual Directories for Websites...follow-up remarks > > >Ok...I see that Virtual Directories work just like I thought they should >for websites that have domains pointing to the server already. > >However, I usually show my clients their websites as they're being >developed by using a direct URL, such as >http://66.xx.xx.138/cfdocs/website/index.cfm. > >That keeps it out of the public eye, yet gives the client access during >the development process. > >Is there a way to do the same thing if I'm using directories not under the >wwwroot? > >Perhaps, a main website with virtual subdirectories for the sites under >development, >such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? > >I'll try that... > >Rick > > > >-- >No virus found in this outgoing message. >Checked by AVG Anti-Virus. >Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195222 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Nothing contained with the cfdocs (as provided by the install) is necessary for operation of the ColdFusion server. In some versions of CF there are security risks in the sample apps that are placed there. While we're on it, you don't want cfide to be publicly accessible either, that's even more significant. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:40 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks Is there any particular reason for removing the cfdocs directory? Space? Any possible complications from not having anything that's in there? Rick -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:24 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks I'd recommended removing the cfdocs directory completely. The documentation is available at livedocs.macromedia.com or from within HomeSite or Dreamweaver. It can also be downloaded from www.macromedia.com. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:07 PM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195223 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
So...do I just move the folder to some other location? Any functional implications for doing that? Rick -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:50 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks Nothing contained with the cfdocs (as provided by the install) is necessary for operation of the ColdFusion server. In some versions of CF there are security risks in the sample apps that are placed there. While we're on it, you don't want cfide to be publicly accessible either, that's even more significant. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:40 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks Is there any particular reason for removing the cfdocs directory? Space? Any possible complications from not having anything that's in there? Rick -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:24 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks I'd recommended removing the cfdocs directory completely. The documentation is available at livedocs.macromedia.com or from within HomeSite or Dreamweaver. It can also be downloaded from www.macromedia.com. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:07 PM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195229 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Agree. If you need cfdocs, keep it on a development server. Use IP restrictions, IIS auth, etc... -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 9:24 AM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks I'd recommended removing the cfdocs directory completely. The documentation is available at livedocs.macromedia.com or from within HomeSite or Dreamweaver. It can also be downloaded from www.macromedia.com. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:07 PM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195231 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Cfide is a bit more tricky because it is required to administer your CF Server. You'll want to set it up on a IIS site that isn't accessible to anyone but yourself. The most straight forward way to accomplish this is set your 'default' site to the IP address of 127.0.0.1 and have your cfide under there. This should make that site only accessible from that box itself. There are additional steps that can be taken, but that's a good start. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 1:00 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks So...do I just move the folder to some other location? Any functional implications for doing that? Rick -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:50 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks Nothing contained with the cfdocs (as provided by the install) is necessary for operation of the ColdFusion server. In some versions of CF there are security risks in the sample apps that are placed there. While we're on it, you don't want cfide to be publicly accessible either, that's even more significant. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:40 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks Is there any particular reason for removing the cfdocs directory? Space? Any possible complications from not having anything that's in there? Rick -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:24 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks I'd recommended removing the cfdocs directory completely. The documentation is available at livedocs.macromedia.com or from within HomeSite or Dreamweaver. It can also be downloaded from www.macromedia.com. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:07 PM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195235 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Rick, Something you may want to consider is to have three instances of a site: dev, test, and production. Dev - where you break a site Test - where they look at a site while you're free to break the one on dev Production - the final site We used to have just a development site and a production site and it was common that we'd ask people to test the development site for us and we'd break it writing new code and they couldn't see it or they'd see things mid-transition. (I personally don't like the word "production" for the final site, but it seems like a common term.) -Kevin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 11:07 AM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195251 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Good idea, Calvin... Thanks, Rick -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 1:13 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks Cfide is a bit more tricky because it is required to administer your CF Server. You'll want to set it up on a IIS site that isn't accessible to anyone but yourself. The most straight forward way to accomplish this is set your 'default' site to the IP address of 127.0.0.1 and have your cfide under there. This should make that site only accessible from that box itself. There are additional steps that can be taken, but that's a good start. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 1:00 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks So...do I just move the folder to some other location? Any functional implications for doing that? Rick -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:50 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks Nothing contained with the cfdocs (as provided by the install) is necessary for operation of the ColdFusion server. In some versions of CF there are security risks in the sample apps that are placed there. While we're on it, you don't want cfide to be publicly accessible either, that's even more significant. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:40 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks Is there any particular reason for removing the cfdocs directory? Space? Any possible complications from not having anything that's in there? Rick -Original Message- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:24 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks I'd recommended removing the cfdocs directory completely. The documentation is available at livedocs.macromedia.com or from within HomeSite or Dreamweaver. It can also be downloaded from www.macromedia.com. - Calvin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 12:07 PM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195258 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Good idea...thanks Kevin... Rick -Original Message- From: Kevin Graeme [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 1:54 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks Rick, Something you may want to consider is to have three instances of a site: dev, test, and production. Dev - where you break a site Test - where they look at a site while you're free to break the one on dev Production - the final site We used to have just a development site and a production site and it was common that we'd ask people to test the development site for us and we'd break it writing new code and they couldn't see it or they'd see things mid-transition. (I personally don't like the word "production" for the final site, but it seems like a common term.) -Kevin -Original Message- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 11:07 AM To: CF-Talk Subject: Virtual Directories for Websites...follow-up remarks Ok...I see that Virtual Directories work just like I thought they should for websites that have domains pointing to the server already. However, I usually show my clients their websites as they're being developed by using a direct URL, such as http://66.xx.xx.138/cfdocs/website/index.cfm. That keeps it out of the public eye, yet gives the client access during the development process. Is there a way to do the same thing if I'm using directories not under the wwwroot? Perhaps, a main website with virtual subdirectories for the sites under development, such as www.MyMainWebsite.com/WebsiteUnderDevelopment ? I'll try that... Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195259 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Virtual Directories for Websites...follow-up remarks
>You mean a different port number for each site under development? > >e.g http://66.79.46.138:85/DevelopmentSite/Index.cfm ? No, it would look like: http://66.79.46.138:85/Index.cfm > >Rick > > >-Original Message- >From: Kwang Suh [mailto:[EMAIL PROTECTED] >Sent: Thursday, February 17, 2005 11:35 AM >To: CF-Talk >Subject: Re: Virtual Directories for Websites...follow-up remarks > > >You can also use different port numbers. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195396 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Hi, Kwang... So, using ports like that would mean there would be no root directory for the websites? i.e., the port would act as the root for the site? I'm not sure I understand the actual directory structure for http://66.79.46.138:85/Index.cfm... Rick -Original Message- From: Kwang Suh [mailto:[EMAIL PROTECTED] Sent: Friday, February 18, 2005 10:44 AM To: CF-Talk Subject: Re: Virtual Directories for Websites...follow-up remarks >You mean a different port number for each site under development? > >e.g http://66.79.46.138:85/DevelopmentSite/Index.cfm ? No, it would look like: http://66.79.46.138:85/Index.cfm > >Rick > > >-Original Message- >From: Kwang Suh [mailto:[EMAIL PROTECTED] >Sent: Thursday, February 17, 2005 11:35 AM >To: CF-Talk >Subject: Re: Virtual Directories for Websites...follow-up remarks > > >You can also use different port numbers. ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195405 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
> So, using ports like that would mean there would be no root directory > for the websites? i.e., the port would act as the root for the site? > I'm not sure I understand the actual directory structure for > http://66.79.46.138:85/Index.cfm... No, you would still need to have separate virtual hosts for each site, and each virtual host would typically have its own root directory. Using different ports just lets you use the same IP address or DNS name to connect to different virtual servers. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195409 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
So, when referencing the "virtual server", I'd just use a URL like http://66.79.46.138:85/Index.cfm because it would take the visitor directly inside the root directory? Am I understanding that correctly? And I guess the key difference is in the properties for the virtual directory, where instead of port 80, port 85 would be specified for the site? And port 85 would have to be opened in the router, too? Rick -Original Message- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Friday, February 18, 2005 12:26 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks > So, using ports like that would mean there would be no root directory > for the websites? i.e., the port would act as the root for the site? > I'm not sure I understand the actual directory structure for > http://66.79.46.138:85/Index.cfm... No, you would still need to have separate virtual hosts for each site, and each virtual host would typically have its own root directory. Using different ports just lets you use the same IP address or DNS name to connect to different virtual servers. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195412 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
> So, when referencing the "virtual server", I'd just use a URL like > http://66.79.46.138:85/Index.cfm because it would take the visitor > directly inside the root directory? Am I understanding that correctly? Yes. > And I guess the key difference is in the properties for the virtual > directory, where instead of port 80, port 85 would be specified for the > site? Yes, except that for the sake of accuracy, this would be a virtual server, not a virtual directory. > And port 85 would have to be opened in the router, too? Yes. I would not recommend this approach for public sites, simply because typing the port in the URL is one more thing that the user has to do to get to your site. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195413 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
One thing that makes life interesting in this case is that the CF root and the Web root will be different. Kevin -Original Message- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: 18 February 2005 17:26 To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks > So, using ports like that would mean there would be no root directory > for the websites? i.e., the port would act as the root for the site? > I'm not sure I understand the actual directory structure for > http://66.79.46.138:85/Index.cfm... No, you would still need to have separate virtual hosts for each site, and each virtual host would typically have its own root directory. Using different ports just lets you use the same IP address or DNS name to connect to different virtual servers. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195415 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Thanks, Dave... Rick -Original Message- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Friday, February 18, 2005 12:41 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks > So, when referencing the "virtual server", I'd just use a URL like > http://66.79.46.138:85/Index.cfm because it would take the visitor > directly inside the root directory? Am I understanding that correctly? Yes. > And I guess the key difference is in the properties for the virtual > directory, where instead of port 80, port 85 would be specified for the > site? Yes, except that for the sake of accuracy, this would be a virtual server, not a virtual directory. > And port 85 would have to be opened in the router, too? Yes. I would not recommend this approach for public sites, simply because typing the port in the URL is one more thing that the user has to do to get to your site. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195419 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Don't think I understand...at least not without a little more thinking about... Care to elaborate on what you mean? Implications? (I assume you're just talking about using a different port scenario only, right?) Rick -Original Message- From: Kevin Roche [mailto:[EMAIL PROTECTED] Sent: Friday, February 18, 2005 12:33 PM To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks One thing that makes life interesting in this case is that the CF root and the Web root will be different. Kevin -Original Message- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: 18 February 2005 17:26 To: CF-Talk Subject: RE: Virtual Directories for Websites...follow-up remarks > So, using ports like that would mean there would be no root directory > for the websites? i.e., the port would act as the root for the site? > I'm not sure I understand the actual directory structure for > http://66.79.46.138:85/Index.cfm... No, you would still need to have separate virtual hosts for each site, and each virtual host would typically have its own root directory. Using different ports just lets you use the same IP address or DNS name to connect to different virtual servers. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195421 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
> One thing that makes life interesting in this case is that the CF root
> and the Web root will be different.
This is the case whenever you have more than one virtual web server using a
single CF server instance, though. To avoid any problems, just don't use the
root CF mapping ("/") within your CFINCLUDE/CFMODULE/etc tags.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software provides the highest caliber vendor-authorized
instruction at our training centers in Washington DC, Atlanta,
Chicago, Baltimore, Northern Virginia, or on-site at your location.
Visit http://training.figleaf.com/ for more information!
~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble
Ticket application
http://www.houseoffusion.com/banners/view.cfm?bannerid=48
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195430
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Dave...
Does the mapping issue become a problem only when the
alternate port is used as a solution?
Rick
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Friday, February 18, 2005 1:42 PM
To: CF-Talk
Subject: RE: Virtual Directories for Websites...follow-up remarks
> One thing that makes life interesting in this case is that the CF root
> and the Web root will be different.
This is the case whenever you have more than one virtual web server using a
single CF server instance, though. To avoid any problems, just don't use the
root CF mapping ("/") within your CFINCLUDE/CFMODULE/etc tags.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software provides the highest caliber vendor-authorized
instruction at our training centers in Washington DC, Atlanta,
Chicago, Baltimore, Northern Virginia, or on-site at your location.
Visit http://training.figleaf.com/ for more information!
~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195436
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Virtual Directories for Websites...follow-up remarks
yes, but in IIS these are called sites. So, for example you have the Default site on port 80 which points http://your.com/ to d:\inetpub\wwwroot\. You can create a new site called say foo listening on port 99 pointing http://your.com:99/ to d:\inetpub\fooroot\ And one step further you can have a different instance of Jrun/CFMX for each of these. :) Doug On Fri, 18 Feb 2005 12:27:21 -0500, Rick Faircloth <[EMAIL PROTECTED]> wrote: > So, when referencing the "virtual server", I'd just use a URL like > http://66.79.46.138:85/Index.cfm because it would take the visitor > directly inside the root directory? Am I understanding that correctly? > > And I guess the key difference is in the properties for the virtual > directory, > where instead of port 80, port 85 would be specified for the site? And > port 85 would have to be opened in the router, too? > > Rick > > > -Original Message- > From: Dave Watts [mailto:[EMAIL PROTECTED] > Sent: Friday, February 18, 2005 12:26 PM > To: CF-Talk > Subject: RE: Virtual Directories for Websites...follow-up remarks > > > So, using ports like that would mean there would be no root directory > > for the websites? i.e., the port would act as the root for the site? > > I'm not sure I understand the actual directory structure for > > http://66.79.46.138:85/Index.cfm... > > No, you would still need to have separate virtual hosts for each site, and > each virtual host would typically have its own root directory. Using > different ports just lets you use the same IP address or DNS name to connect > to different virtual servers. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > > Fig Leaf Software provides the highest caliber vendor-authorized > instruction at our training centers in Washington DC, Atlanta, > Chicago, Baltimore, Northern Virginia, or on-site at your location. > Visit http://training.figleaf.com/ for more information! > > ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195437 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
Thanks for the info, Doug... Rick -Original Message- From: Douglas Knudsen [mailto:[EMAIL PROTECTED] Sent: Friday, February 18, 2005 1:49 PM To: CF-Talk Subject: Re: Virtual Directories for Websites...follow-up remarks yes, but in IIS these are called sites. So, for example you have the Default site on port 80 which points http://your.com/ to d:\inetpub\wwwroot\. You can create a new site called say foo listening on port 99 pointing http://your.com:99/ to d:\inetpub\fooroot\ And one step further you can have a different instance of Jrun/CFMX for each of these. :) Doug On Fri, 18 Feb 2005 12:27:21 -0500, Rick Faircloth <[EMAIL PROTECTED]> wrote: > So, when referencing the "virtual server", I'd just use a URL like > http://66.79.46.138:85/Index.cfm because it would take the visitor > directly inside the root directory? Am I understanding that correctly? > > And I guess the key difference is in the properties for the virtual > directory, > where instead of port 80, port 85 would be specified for the site? And > port 85 would have to be opened in the router, too? > > Rick > > > -Original Message- > From: Dave Watts [mailto:[EMAIL PROTECTED] > Sent: Friday, February 18, 2005 12:26 PM > To: CF-Talk > Subject: RE: Virtual Directories for Websites...follow-up remarks > > > So, using ports like that would mean there would be no root directory > > for the websites? i.e., the port would act as the root for the site? > > I'm not sure I understand the actual directory structure for > > http://66.79.46.138:85/Index.cfm... > > No, you would still need to have separate virtual hosts for each site, and > each virtual host would typically have its own root directory. Using > different ports just lets you use the same IP address or DNS name to connect > to different virtual servers. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > > Fig Leaf Software provides the highest caliber vendor-authorized > instruction at our training centers in Washington DC, Atlanta, > Chicago, Baltimore, Northern Virginia, or on-site at your location. > Visit http://training.figleaf.com/ for more information! > > ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195453 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Virtual Directories for Websites...follow-up remarks
> Does the mapping issue become a problem only when the > alternate port is used as a solution? No, it's an issue whenever you have more than one virtual web server using a single CF server instance. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195462 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
