How to create a development area
Permalink
My client has a web site already on ix web hosting which we want to leave there until we have the new site up and running.
The new site will be at blue host using the concrete5 tool. When i installed the tool it asked for a domain name which i put in, but now it point to the current site.
How can i have concrete5 point to the new files at bluehost which when they new site is done we will change the domain name to point to blue host.
Do i need to buy a new domain to use for development? and then change the domain name to the development name? When i'm done how hard is it then do change the domain name back.
First time user for concrete 5, any help would be much appreciated.
Thanks
Maggie
The new site will be at blue host using the concrete5 tool. When i installed the tool it asked for a domain name which i put in, but now it point to the current site.
How can i have concrete5 point to the new files at bluehost which when they new site is done we will change the domain name to point to blue host.
Do i need to buy a new domain to use for development? and then change the domain name to the development name? When i'm done how hard is it then do change the domain name back.
First time user for concrete 5, any help would be much appreciated.
Thanks
Maggie
Can you recommend which is the best way to handle this. There may be several people working on the new site (concrete5 tool) and don't want them to change anything on the live site by accident.
1. Keep files at current hosting with their domain (live site) so nothing gets disturbed.
2. Purchase new domain so we can do our new design and put files up as we use them and nothing can be confused with the original site. The new files will be at the new hosting, I would then just point the domain name to the new hosting and it should pick up all the information and database? I wouldn't have to do anything else then? right?
3. Move current site, set up sub domain (development.mycurrentdomain) and work there.
Question here is does c5 users only see the development area (folder) so there can be no accidents with changing the current site.
When we're done with the new site how does the database see the new files when we change c5 back to the regular domain name (w/o the sub domain).
Just don't want to be half way into the new site and realize it may take more time to get it working properly at the end.
Thanks
Maggie
1. Keep files at current hosting with their domain (live site) so nothing gets disturbed.
2. Purchase new domain so we can do our new design and put files up as we use them and nothing can be confused with the original site. The new files will be at the new hosting, I would then just point the domain name to the new hosting and it should pick up all the information and database? I wouldn't have to do anything else then? right?
3. Move current site, set up sub domain (development.mycurrentdomain) and work there.
Question here is does c5 users only see the development area (folder) so there can be no accidents with changing the current site.
When we're done with the new site how does the database see the new files when we change c5 back to the regular domain name (w/o the sub domain).
Just don't want to be half way into the new site and realize it may take more time to get it working properly at the end.
Thanks
Maggie
Option 1 and 2 appear to be the safest things to do in this situation. Once you are ready to go live, just change your DNS settings of the domain to point to the new host. You will probably have to make some edits to /config/site.php too (likely just change the base URL).
Hope that helps.
Hope that helps.
Otherwise, you could copy the old files from the old host to the new host, then change the DNS settings of the domain to point to the new host.
Afterward, you could set up a subdomain (eg: subdomain.iownthisurl.com) and set up Concrete5 there.
When you are ready to move your site, check out this how to:
http://www.concrete5.org/documentation/installation/moving_a_site...