From test domain to public domain
Permalink
Hello!
I'm creating several websites with Concrete5. Love that you can focus on editing content, and not worry about HTML, ftps, etc. (thanks guys!).
I have a question.
Since I'm new to this, I am using test domains, such ashttp://www.example.com/test (see:www.www.open3dtraining.com/3dtraining),... but eventually I'll want to move that to the main website, sohttp://www.example.com (in my case:http://www.open3dtraining.com andhttp://www.tuenglishclass.com).
How can I go about this?
--
Also, say I have my site created onwww.www.open3dtraining.com/3dtraining... and eventually I want to move THAT concrete5 directory elsewhere, and have a NEW concrete5 page in that SAME directory...
How can I go about that?
Thanks!
I'm creating several websites with Concrete5. Love that you can focus on editing content, and not worry about HTML, ftps, etc. (thanks guys!).
I have a question.
Since I'm new to this, I am using test domains, such ashttp://www.example.com/test (see:www.www.open3dtraining.com/3dtraining),... but eventually I'll want to move that to the main website, sohttp://www.example.com (in my case:http://www.open3dtraining.com andhttp://www.tuenglishclass.com).
How can I go about this?
--
Also, say I have my site created onwww.www.open3dtraining.com/3dtraining... and eventually I want to move THAT concrete5 directory elsewhere, and have a NEW concrete5 page in that SAME directory...
How can I go about that?
Thanks!
I think there are some tutorials on this topic that go step by step but I'll just chime in that sometimes those details actually make the process of moving a site seem more complicated. I just focus on 2 things, getting all the files to the correct location, importing the database and updating that database connection (if the details changed during the migration). Anything else that might cause an issue, like updating config settings, base url, htaccess etc., can be debugged after if there is a problem.
Many developers seem to suggest making a fresh install at the new location as part of the migration process. I'm not saying they are wrong but I don't do that, because if a site is working at location A, I want to pick it up and drop it into location B, not install a new site and then tinker with pieces of it. Move all the files, move the entire database, and you should be for the most part done.
So to summarize:
1) Bundle your files (zip/tar) and move them to their new location.
2) Export your database, import to the new location.
3) Update the database connection file in /config/site.php if that database connection has changed.
4) Test the site, if there are problems start debugging.
Many developers seem to suggest making a fresh install at the new location as part of the migration process. I'm not saying they are wrong but I don't do that, because if a site is working at location A, I want to pick it up and drop it into location B, not install a new site and then tinker with pieces of it. Move all the files, move the entire database, and you should be for the most part done.
So to summarize:
1) Bundle your files (zip/tar) and move them to their new location.
2) Export your database, import to the new location.
3) Update the database connection file in /config/site.php if that database connection has changed.
4) Test the site, if there are problems start debugging.
Thanks guys, I'll def check it out soon.
http://www.concrete5.org/community/forums/customizing_c5/move-a-con...