Re: RE: I think I'm confused...
Jason Fisher's answer is exactly what I'd do. IIS configuration (assuming you're using IIS) is actually the more tedious step. Perhaps adding an additional IP to your NIC and pointing your Hosts records at it would provide simple configuration of IIS for this monster domain app (routing by IP rather than host header). I'll test it. On Feb 24, 2011 8:29am, Rick Faircloth r...@whitestonemedia.com wrote: One solution is to have a table of sub-domains that refer to the main application config table: lookup domain.com or blog.domain.com or www.domain.com and find the parent config record for www.domain.com. In that case, you can then add dev.domain.com to the sub-domain table, but you'd still have to have the dev.domain.com entry in your local hosts file for it to work. Boy that's starting to get complicated. I'm already, even before actually starting, to long for the days of single, isolated websites. I would tend to ignore the subdomains for now, except for the fact that subdomains using mobile are coming on so strong and are part of my application-building plan... mobile.xyz.com. It seems, especially with the mobile dev world, that it would be a lot simpler, and perhaps more efficient in the end, to have one MSOC app for desktop sites and another MSOC app for the same site in a mobile version. I'm going to have to think on this one for awhile to come up with a sound, long-term (as long as possible in this fast changing landscape) plan. I don't want to get half-way down this path of app development and then realize I need to start all over. Perhaps some of you smart people on the list could blog (in-depth) about how to go about this (in detail!). Rick ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342560 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Re: RE: I think I'm confused...
I just confirmed that this idea works. The only downside is your NIC will require static IP addresses. On Feb 24, 2011 8:38am, jqdur...@gmail.com wrote: Jason Fisher's answer is exactly what I'd do. IIS configuration (assuming you're using IIS) is actually the more tedious step. Perhaps adding an additional IP to your NIC and pointing your Hosts records at it would provide simple configuration of IIS for this monster domain app (routing by IP rather than host header). I'll test it. On Feb 24, 2011 8:29am, Rick Faircloth r...@whitestonemedia.com wrote: One solution is to have a table of sub-domains that refer to the main application config table: lookup domain.com or blog.domain.com or www.domain.com and find the parent config record for www.domain.com. In that case, you can then add dev.domain.com to the sub-domain table, but you'd still have to have the dev.domain.com entry in your local hosts file for it to work. Boy that's starting to get complicated. I'm already, even before actually starting, to long for the days of single, isolated websites. I would tend to ignore the subdomains for now, except for the fact that subdomains using mobile are coming on so strong and are part of my application-building plan... mobile.xyz.com. It seems, especially with the mobile dev world, that it would be a lot simpler, and perhaps more efficient in the end, to have one MSOC app for desktop sites and another MSOC app for the same site in a mobile version. I'm going to have to think on this one for awhile to come up with a sound, long-term (as long as possible in this fast changing landscape) plan. I don't want to get half-way down this path of app development and then realize I need to start all over. Perhaps some of you smart people on the list could blog (in-depth) about how to go about this (in detail!). Rick ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342562 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: RE: I think I'm confused...
Why not use mydomain.com.dev? Then just strip off the .dev before using the server name variable while in production. This doesn't really seem like that big of a hurdle. On Feb 24, 2011 8:38am, Rick Faircloth r...@whitestonemedia.com wrote: Perhaps a good approach might be to use fictitious domains locally, since I'm planning to develop sites that are void of client content until the client works with the app to supply every piece of data and asset. That way, I avoid using any client assets in development locally, isolating the local-development app from the client-facing app. That minimizes editing of the host file and I don't have to bother with making sure client assets, either database or files, get transferred to the server. Sigh... so many possibilities... too many, actually. -Original Message- From: Jason Fisher [mailto:ja...@wanax.com] Sent: Thursday, February 24, 2011 8:15 AM To: cf-talk Subject: RE: I think I'm confused... One solution is to have a table of sub-domains that refer to the main application config table: lookup domain.com or blog.domain.com or www.domain.com and find the parent config record for www.domain.com. In that case, you can then add dev.domain.com to the sub-domain table, but you'd still have to have the dev.domain.com entry in your local hosts file for it to work. From: Rick Faircloth Sent: Thursday, February 24, 2011 8:01 AM To: cf-talk cf-talk@houseoffusion.com Subject: RE: I think I'm confused... I could easily see that working for single sites, but if I'm developing a multiple sites, one codebase application that depends on reading specific domain names for setting sites variables, that means I have to have those dev.mydomain domains in the local hosts file, as well. I could just use the mydomain part of the url for identification, but as someone pointed out earlier in the MSOC discussion, that wouldn't account for subdomains, if they're used, such as blog.mydomain, etc. Any thoughts on this concern? Rick -Original Message- From: Mike Kear [mailto:afpwebwo...@gmail.com] Sent: Thursday, February 24, 2011 6:04 AM To: cf-talk Subject: Re: I think I'm confused... I use different domain names. I have www.mydomain.com for the live server site, and dev.mydomain for my local development sites Then in my hosts file, i have the line: 127.0.0.1 dev.mydomain for each client site i have. With apache, the local dev versions and remote server versions behave in an identical manner Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion 9 Enterprise, PHP, ASP, ASP.NET hosting from AUD$15/month On Thu, Feb 24, 2011 at 9:21 PM, Rick Faircloth r...@whitestonemedia.com wrote: Ok... thanks Mark and Eric We need a better solution available to developers to be able to switch between local and server DNS. Perhaps, a switch of some kind that could be inserted into a URL to tell a browser to use a local hosts file if that switch is present. http://local/www.xyz.com or http://l:www.xyz.com That would certainly be a *lot* easier than constantly editing that hosts file. But it's good to know that I can use a local DNS file that way! ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342565 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Re: RE: I think I'm confused...
Oops... typo. You will only see .dev in DEVELOPMENT. Therefore, you'll need to strip it off in development, rather than production. On Feb 24, 2011 8:47am, jqdur...@gmail.com wrote: Why not use mydomain.com.dev? Then just strip off the .dev before using the server name variable while in production. This doesn't really seem like that big of a hurdle. On Feb 24, 2011 8:38am, Rick Faircloth r...@whitestonemedia.com wrote: Perhaps a good approach might be to use fictitious domains locally, since I'm planning to develop sites that are void of client content until the client works with the app to supply every piece of data and asset. That way, I avoid using any client assets in development locally, isolating the local-development app from the client-facing app. That minimizes editing of the host file and I don't have to bother with making sure client assets, either database or files, get transferred to the server. Sigh... so many possibilities... too many, actually. -Original Message- From: Jason Fisher [mailto:ja...@wanax.com] Sent: Thursday, February 24, 2011 8:15 AM To: cf-talk Subject: RE: I think I'm confused... One solution is to have a table of sub-domains that refer to the main application config table: lookup domain.com or blog.domain.com or www.domain.com and find the parent config record for www.domain.com. In that case, you can then add dev.domain.com to the sub-domain table, but you'd still have to have the dev.domain.com entry in your local hosts file for it to work. From: Rick Faircloth Sent: Thursday, February 24, 2011 8:01 AM To: cf-talk cf-talk@houseoffusion.com Subject: RE: I think I'm confused... I could easily see that working for single sites, but if I'm developing a multiple sites, one codebase application that depends on reading specific domain names for setting sites variables, that means I have to have those dev.mydomain domains in the local hosts file, as well. I could just use the mydomain part of the url for identification, but as someone pointed out earlier in the MSOC discussion, that wouldn't account for subdomains, if they're used, such as blog.mydomain, etc. Any thoughts on this concern? Rick -Original Message- From: Mike Kear [mailto:afpwebwo...@gmail.com] Sent: Thursday, February 24, 2011 6:04 AM To: cf-talk Subject: Re: I think I'm confused... I use different domain names. I have www.mydomain.com for the live server site, and dev.mydomain for my local development sites Then in my hosts file, i have the line: 127.0.0.1 dev.mydomain for each client site i have. With apache, the local dev versions and remote server versions behave in an identical manner Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion 9 Enterprise, PHP, ASP, ASP.NET hosting from AUD$15/month On Thu, Feb 24, 2011 at 9:21 PM, Rick Faircloth r...@whitestonemedia.com wrote: Ok... thanks Mark and Eric We need a better solution available to developers to be able to switch between local and server DNS. Perhaps, a switch of some kind that could be inserted into a URL to tell a browser to use a local hosts file if that switch is present. http://local/www.xyz.com or http://l:www.xyz.com That would certainly be a *lot* easier than constantly editing that hosts file. But it's good to know that I can use a local DNS file that way! ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342566 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
RE: RE: I think I'm confused...
I eagerly await your test results! (and further details!) :o) -Original Message- From: jqdur...@gmail.com [mailto:jqdur...@gmail.com] Sent: Thursday, February 24, 2011 9:39 AM To: cf-talk Subject: Re: RE: I think I'm confused... Jason Fisher's answer is exactly what I'd do. IIS configuration (assuming you're using IIS) is actually the more tedious step. Perhaps adding an additional IP to your NIC and pointing your Hosts records at it would provide simple configuration of IIS for this monster domain app (routing by IP rather than host header). I'll test it. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342570 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
RE: Re: RE: I think I'm confused...
Bummer... I'm not sure I can get a static IP address. I've currently got a business-class DSL line running for which I could probably get a static IP for additional cost. However, I just responded to a proposal from Comcast to user cable broadband at higher rates at half the price of the DSL. But I don't believe I can get a static IP from Comcast. And I hate complicating things the DynDns.com or something similar. Maybe in the end that would be preferable. Now, how would this work in the local hosts file setup that is really different from using 127.0.0.1? Wouldn't the second IP still be referenced only locally? Or are you talking about using the second IP externally with the development domains setup with external DNS and pointing to the second IP on my dev machine, which would be acting as an externally accessible dev server? -Original Message- From: jqdur...@gmail.com [mailto:jqdur...@gmail.com] Sent: Thursday, February 24, 2011 9:46 AM To: cf-talk Subject: Re: Re: RE: I think I'm confused... I just confirmed that this idea works. The only downside is your NIC will require static IP addresses. On Feb 24, 2011 8:38am, jqdur...@gmail.com wrote: Jason Fisher's answer is exactly what I'd do. IIS configuration (assuming you're using IIS) is actually the more tedious step. Perhaps adding an additional IP to your NIC and pointing your Hosts records at it would provide simple configuration of IIS for this monster domain app (routing by IP rather than host header). I'll test it. On Feb 24, 2011 8:29am, Rick Faircloth r...@whitestonemedia.com wrote: One solution is to have a table of sub-domains that refer to the main application config table: lookup domain.com or blog.domain.com or www.domain.com and find the parent config record for www.domain.com. In that case, you can then add dev.domain.com to the sub-domain table, but you'd still have to have the dev.domain.com entry in your local hosts file for it to work. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342572 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
RE: RE: I think I'm confused...
Yes, that seems like it would work as well as pre-pending local as Steve suggested: local.www.domain.com or www.domain.com.dev. Either of these would work as long as local dev is kept entirely separate from production in terms of variables, etc, which would be dependent on the actual domain name. (Without setting up parsing code to handle the domain variations) -Original Message- From: jqdur...@gmail.com [mailto:jqdur...@gmail.com] Sent: Thursday, February 24, 2011 9:48 AM To: cf-talk Subject: Re: RE: I think I'm confused... Why not use mydomain.com.dev? Then just strip off the .dev before using the server name variable while in production. This doesn't really seem like that big of a hurdle. On Feb 24, 2011 8:38am, Rick Faircloth r...@whitestonemedia.com wrote: Perhaps a good approach might be to use fictitious domains locally, since I'm planning to develop sites that are void of client content until the client works with the app to supply every piece of data and asset. That way, I avoid using any client assets in development locally, isolating the local-development app from the client-facing app. That minimizes editing of the host file and I don't have to bother with making sure client assets, either database or files, get transferred to the server. Sigh... so many possibilities... too many, actually. -Original Message- From: Jason Fisher [mailto:ja...@wanax.com] Sent: Thursday, February 24, 2011 8:15 AM To: cf-talk Subject: RE: I think I'm confused... One solution is to have a table of sub-domains that refer to the main application config table: lookup domain.com or blog.domain.com or www.domain.com and find the parent config record for www.domain.com. In that case, you can then add dev.domain.com to the sub-domain table, but you'd still have to have the dev.domain.com entry in your local hosts file for it to work. From: Rick Faircloth Sent: Thursday, February 24, 2011 8:01 AM To: cf-talk cf-talk@houseoffusion.com Subject: RE: I think I'm confused... I could easily see that working for single sites, but if I'm developing a multiple sites, one codebase application that depends on reading specific domain names for setting sites variables, that means I have to have those dev.mydomain domains in the local hosts file, as well. I could just use the mydomain part of the url for identification, but as someone pointed out earlier in the MSOC discussion, that wouldn't account for subdomains, if they're used, such as blog.mydomain, etc. Any thoughts on this concern? Rick -Original Message- From: Mike Kear [mailto:afpwebwo...@gmail.com] Sent: Thursday, February 24, 2011 6:04 AM To: cf-talk Subject: Re: I think I'm confused... I use different domain names. I have www.mydomain.com for the live server site, and dev.mydomain for my local development sites Then in my hosts file, i have the line: 127.0.0.1 dev.mydomain for each client site i have. With apache, the local dev versions and remote server versions behave in an identical manner Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion 9 Enterprise, PHP, ASP, ASP.NET hosting from AUD$15/month On Thu, Feb 24, 2011 at 9:21 PM, Rick Faircloth r...@whitestonemedia.com wrote: Ok... thanks Mark and Eric We need a better solution available to developers to be able to switch between local and server DNS. Perhaps, a switch of some kind that could be inserted into a URL to tell a browser to use a local hosts file if that switch is present. http://local/www.xyz.com or http://l:www.xyz.com That would certainly be a *lot* easier than constantly editing that hosts file. But it's good to know that I can use a local DNS file that way! ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342574 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
RE: Re: RE: I think I'm confused...
I guess I could use: local.domain01.com local.domain02.com dev.domain01.com dev.domain02.com www.domain01.com www.domain01.com But as I've been thinking here, if I keep the local variables and assets completely separate from the production side, any local domains can be used without complication, it seems. local.domain01.com local.domain02.com dev.domain01.com dev.domain02.com (The variables and assets would be exactly the same for local and dev levels. The functionality and assets would just be tested externally on the dev side) Then, for production, actual client domains are used: www.clientDomain01.com www.clientDomain02.com Seem right? -Original Message- From: jqdur...@gmail.com [mailto:jqdur...@gmail.com] Sent: Thursday, February 24, 2011 9:49 AM To: cf-talk Subject: Re: Re: RE: I think I'm confused... Oops... typo. You will only see .dev in DEVELOPMENT. Therefore, you'll need to strip it off in development, rather than production. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342575 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
