Hi everyone,

Has DNN (or any DNN user) ever come up with a method for "hiding" a DNN site while under development? The only method I've read about is to make a simple page and assign it "Home page" status, then keep all other pages permissions to admin only. That seems very clunky. Surely, over the years, some other method has emerged.

Thanks for any info offered.

Jim

We use a couple of methods for DNNSoftware.  For staging sites we don't create a DNS entry for the site.  Instead we use an entry in our HOST file to associate hit a particular IP address.  The other way we have done it in our cloud environment is to put the dev site on a different port.  The same domain URL on port 80 can serve the current live site.  When it comes time to make the switch, stop the live site and change the Port binding for the dev site.  This allows you to even pre-warm up the dev site when you are ready to make it live since it doesn't require an App Recycle to change the port.