Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
v1.4:practices [2010/04/28 12:41]
Reines
v1.4:practices [2010/10/17 18:45] (current)
Line 15: Line 15:
   - Take a copy of the database.   - Take a copy of the database.
     * For MySQL:     * For MySQL:
-      * Using [[http://​www.phpmyadmin.net|PHPMyAdmin]]. ([[:​phpmyadmin#​backing-up-a-database|instructions]])+      * Using [[http://​www.phpmyadmin.net|phpMyAdmin]]. ([[:​phpmyadmin#​backing-up-a-database|instructions]])
       * Using [[http://​linux.die.net/​man/​1/​mysqldump|mysqldump]]:​ ''​mysqldump -u <​user>​ -p <db name> | gzip -f > backup.sql.gz''​ (where ''<​user>''​ is your MySQL username and ''<​db name>''​ is your forum database name)       * Using [[http://​linux.die.net/​man/​1/​mysqldump|mysqldump]]:​ ''​mysqldump -u <​user>​ -p <db name> | gzip -f > backup.sql.gz''​ (where ''<​user>''​ is your MySQL username and ''<​db name>''​ is your forum database name)
     * For PostgreSQL:     * For PostgreSQL:
Line 23: Line 23:
       * Simply take a copy of your database file as in step 1.       * Simply take a copy of your database file as in step 1.
  
-**Note:** Unless you are comfortable with *nix I would recommend using a FTP client and PHPMyAdmin/​PHPPgAdmin.+**Note:** Unless you are comfortable with *nix I would recommend using a FTP client and phpMyAdmin/​PHPPgAdmin.
 ==== Automated backup ==== ==== Automated backup ====
 The main problem with backing up is usually people get lazy and stop taking regular backups. The obvious solution is to use an automated backup procedure. The main problem with backing up is usually people get lazy and stop taking regular backups. The obvious solution is to use an automated backup procedure.