Usually I simply place a website that I’m building onto one of my obscure fish-related URLs and then transfer it across to the real thing when I’m ready.
With this site however there are some reasons why I’d like to get it on the real URL sooner rather than later, so I’m looking for a way of ‘hiding’ it from anyone who might inadvertently stumble across it. There are no secrets, it’s just to prevent anyone seeing the development site.
I’d like to keep it simple - really simple - and wondered what people thought was the best way to do this? Ideally so when the time comes I can ‘flick a switch’ and it’s all there, visible and ready to go.
Not sure who you host with, but if it’s Chillidog they have a really easy and neat way of password protecting a site in their control panel. You can give access to your client so they can review during build, and when it’s time to go live you just remove the password.
I didn’t know it was there until I stumbled across it one day!
Server Side - the folder stays protected for as long as you have the password applied to the folder in the Control Panel.
Browser Side - It appears to me that for a user who enters a correct password they then don’t have to re-enter the password until the browser cache is refreshed, but @barchard would probably need to confirm that.
For me it works with a RW site to place the site under development simply in a sub-folder, leave the main folder empty and eventually restrict search engines.
In the end, delete the site under development and re-publish.
I also like developing everything under a subdomain. I prefer that to a subfolder myself. You may also want to make sure that you setup a robots.txt so that search engines do not source that new test site.
To get the logins between pages to integrate, you simply need to set the pagesafe ID to be the same. If you use different pagesafe Ids, then the logins are kept separate and you will need to know the passcode for each.