Tranferring Site
Permalink
Hi Guys
Here's the issue. I generally setup a test directory for each new concrete site i make where the client can see the design, and features and i tweak the site to their liking.
However, increasingly clients want to populate this test site with data and then be to switch it live= fair request.
What i need to know is if I turn the test directory into the one targeted by a new addon domain, i.e. the client's live domain, what (precisely) would I need to change in terms of the concrete setup files and database?
Is everything simply routed through the config file and therefore I just need to chagne the base paths. Or are there any paths stored in the database that i would need to change?
Any advice here would be extremely helpful.
many thanks,
Jeb
Here's the issue. I generally setup a test directory for each new concrete site i make where the client can see the design, and features and i tweak the site to their liking.
However, increasingly clients want to populate this test site with data and then be to switch it live= fair request.
What i need to know is if I turn the test directory into the one targeted by a new addon domain, i.e. the client's live domain, what (precisely) would I need to change in terms of the concrete setup files and database?
Is everything simply routed through the config file and therefore I just need to chagne the base paths. Or are there any paths stored in the database that i would need to change?
Any advice here would be extremely helpful.
many thanks,
Jeb
config.php, .htaccess, and any maybe some links within text.
Oh well that sounds almost too easy. Where's the catch? :)
The catch is if you move hosts, rather than just shuffle round within a host. Then you have to worry about files and windows to linux issues.
Ahh i see. Thanks mate that helps a lot.
I'm justing really going to be renaming the parent directory and pointing a domain at it so nothing much needs to change. I wasn't sure if there was any path info stored in one of the bazillion tables that get created on a concrete install hehe.
I'm justing really going to be renaming the parent directory and pointing a domain at it so nothing much needs to change. I wasn't sure if there was any path info stored in one of the bazillion tables that get created on a concrete install hehe.
Personally I work in a parallel directory to an existing domain with a subdomain.
eg:
mysite.com points to /existingsite/....
new.mysite.com points to /c5site/.....
To deploy, I adjust the domains so
oldsite.mysite.com points to /existingsite/......
mysite.com points to /c5site/.....
Then, once all is stable and I know I will never want to revert, I can delete the subomains and old site files.
eg:
mysite.com points to /existingsite/....
new.mysite.com points to /c5site/.....
To deploy, I adjust the domains so
oldsite.mysite.com points to /existingsite/......
mysite.com points to /c5site/.....
Then, once all is stable and I know I will never want to revert, I can delete the subomains and old site files.
