This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
May 12, 2011 7:39am
Subscribe [2]#1 / May 12, 2011 7:39am
Run into this issue a few times and wondered if anyone had a nifty solution? One host I use a lot uses an IP address/~username scenario until your DNS propagates. I haven’t been able to install or run EE this way, instead using a temporary domain/alias instead. It’s no biggie, but it would be much simpler if EE could run on the IP until I’m ready to go live.
Your thoughts folks?
#2 / May 12, 2011 6:22pm
Hi, Ian. What I do is edit my hosts file to point the IP address to the coming soon domain name. It makes it a bit harder for clients to see, but a lot easier for you to work with.
Does that help?
#3 / May 13, 2011 4:59am
Thanks Sue, although I think that might baffle my clients. I’ve gone the temporary domain route instead.
#4 / May 13, 2011 5:47am
Hi, Ian.
I agree, if you need to involve clients, then a temporary domain name is the way to go. That’s how EngineHosting sets things up initially. Makes it a LOT easier to do things.
If anything else comes up, please do let us know in a new thread..