Building on live server alongside existing HTML website, alternative
Permalink
1. Can I install Concrete5 on my server and develop a C5 website alongside an existing HTML version? I'm guessing 'yes', but how do I guarantee it will be 'dark' until I want it to go live?
A. Will a robots.txt disallow be sufficient to keep the C5 version hidden?
B. If I use the C5 dashboard to keep the C5 site private, can I still work on it and preview it in that state?
C. If I connect my C5 version to the Concrete5 community, does that conflict with it being private for now?
2. If I develop my C5 website within a Bitnami C5 stack on my Mac, how do I then move it to the server?
A. Will a robots.txt disallow be sufficient to keep the C5 version hidden?
B. If I use the C5 dashboard to keep the C5 site private, can I still work on it and preview it in that state?
C. If I connect my C5 version to the Concrete5 community, does that conflict with it being private for now?
2. If I develop my C5 website within a Bitnami C5 stack on my Mac, how do I then move it to the server?
Best way would be to put it in a sub-folder and use an .htaccess file to limit access to it with a username/password protect it.
Hi,
It kind of depends, how your current server folders look. If the current page is within a subfolder of the webroot, you could change the domain to point to the webroot and then redirect all users to the existing page within the subfolder using .htaccess. Then you can specifiy certain ip's within the .htaccess, which will not be redirected.
Connecting the site to the community should not be a problem, since you call the link to connect the site troughout the site and so it will work.
If your current page lives in the webroot, you will need to put concrete5 in a subfolder and when the site goes live, you need to change the domain to point to that subfolder or add a .htaccess redirect. Although, your site will keep showing the url mydomain.com/mysubfolder and you might need to reconnect the page since there is no option to edit the url.. In that case, as Keeasti mentioned, protecting it with .htaccess is fine..
It kind of depends, how your current server folders look. If the current page is within a subfolder of the webroot, you could change the domain to point to the webroot and then redirect all users to the existing page within the subfolder using .htaccess. Then you can specifiy certain ip's within the .htaccess, which will not be redirected.
Connecting the site to the community should not be a problem, since you call the link to connect the site troughout the site and so it will work.
If your current page lives in the webroot, you will need to put concrete5 in a subfolder and when the site goes live, you need to change the domain to point to that subfolder or add a .htaccess redirect. Although, your site will keep showing the url mydomain.com/mysubfolder and you might need to reconnect the page since there is no option to edit the url.. In that case, as Keeasti mentioned, protecting it with .htaccess is fine..
