Migrating locally and back - Joomla! Forum - community, help and support
hello helpful people,
i have lost 1 of client's web sites due database copy error --two months of work lost. keep hearing shouldn't working on live site, reason. moving forward, develop locally (offline) upload updated site files, , make switch. after several days of trial/error searching web, haven't found step-by-step outlines how it. ---can please point me in right direction? ...surely information out there somewhere.
my details:
joomla! 2.5.*
xampp installed , running apache , mysql services
site files ftp'd fatcow put in xampp/htdocs locally
database exported , imported via phpmyadmin
---not type in address bar. tried localhost/foldername/index.php says couldn't connect.
***please don't akeeba. spent 2 days trying install , couldn't show in backend ---what horrible software.
2nd question... assume need change database name in configuration.php , phpmyadmin?---so when upload again don't overwrite live site files.
any appreciated.
-adam
my configuration.php settings:
$host = 'localhost';
$user = 'didnotchange';
$password = 'alsodidnotchange';
$db = 'newdbname'; /**the new name specified in phpmyadmin change db name utility**/
$log_path = 'var/www/foldername/logs'; /**same sitename**/
$tmp_path = 'var/www/foldername/tmp'; /**same sitename**/
i have lost 1 of client's web sites due database copy error --two months of work lost. keep hearing shouldn't working on live site, reason. moving forward, develop locally (offline) upload updated site files, , make switch. after several days of trial/error searching web, haven't found step-by-step outlines how it. ---can please point me in right direction? ...surely information out there somewhere.
my details:
joomla! 2.5.*
xampp installed , running apache , mysql services
site files ftp'd fatcow put in xampp/htdocs locally
database exported , imported via phpmyadmin
---not type in address bar. tried localhost/foldername/index.php says couldn't connect.
***please don't akeeba. spent 2 days trying install , couldn't show in backend ---what horrible software.
2nd question... assume need change database name in configuration.php , phpmyadmin?---so when upload again don't overwrite live site files.
any appreciated.
-adam
my configuration.php settings:
$host = 'localhost';
$user = 'didnotchange';
$password = 'alsodidnotchange';
$db = 'newdbname'; /**the new name specified in phpmyadmin change db name utility**/
$log_path = 'var/www/foldername/logs'; /**same sitename**/
$tmp_path = 'var/www/foldername/tmp'; /**same sitename**/
it sucks learned lesson hard way, know never again.
1)work on live sites before do, take backup
2)work offline , migrate site online
try akeeba backup, extension designed backups , port production live or migrate servers in general. it's free , has lot of features, paid version has more features , recommend if doing lot of website work (remote backups, restore admin panel, transfer admin panel, , more).
for free version, have free script called kickstart extract archive , install of joomla on new server saving time , effort it's nice.
you need of new access credentials though.
you can full mysql , file backups. if you're working on shared hosting might have split archive several pieces because of shared hosting limitations. have excellent tutorials , documentation.
if choose manually have is:
1)copy files server (ftp transfer mode set binary, or you'll corrupt files)
2)export mysql database (supress foreign key checks) using phpmyadmin or mysql itself
3)import mysql new db
4)change configuration.php have new settings
hope helps, i'd go akeeba backup. installed on client sites , can cron backups have snapshots of site available in case goes wrong. has restore points when install extensions , etc...very advanced , amazing!
ps. transferring files 1 one slow, akeeba uses single or multi-part archive (joomla has hundreds or thousands of files) it's faster. if manually try making archive (zip, rar, etc.) , extracting on server go faster...shared hosting might not allow though.
1)work on live sites before do, take backup
2)work offline , migrate site online
try akeeba backup, extension designed backups , port production live or migrate servers in general. it's free , has lot of features, paid version has more features , recommend if doing lot of website work (remote backups, restore admin panel, transfer admin panel, , more).
for free version, have free script called kickstart extract archive , install of joomla on new server saving time , effort it's nice.
you need of new access credentials though.
you can full mysql , file backups. if you're working on shared hosting might have split archive several pieces because of shared hosting limitations. have excellent tutorials , documentation.
if choose manually have is:
1)copy files server (ftp transfer mode set binary, or you'll corrupt files)
2)export mysql database (supress foreign key checks) using phpmyadmin or mysql itself
3)import mysql new db
4)change configuration.php have new settings
hope helps, i'd go akeeba backup. installed on client sites , can cron backups have snapshots of site available in case goes wrong. has restore points when install extensions , etc...very advanced , amazing!
ps. transferring files 1 one slow, akeeba uses single or multi-part archive (joomla has hundreds or thousands of files) it's faster. if manually try making archive (zip, rar, etc.) , extracting on server go faster...shared hosting might not allow though.
Comments
Post a Comment