mysql-wordpress-dump v1.0.8
Installation
Using npm:
$ npm i --save mysql-wordpress-dumpUse in Node.js
Config File
'use strict'
const StorageClass = require('mysql-wordpress-dump').storage
module.exports = {
mysql: {
production: {
storageOne: new StorageClass('host', 'user', 'password', 'port', 'database')
},
develop: {
storageDevOne: new StorageClass('host', 'user', 'password', 'port', 'database')
}
},
wordpress: {
production: {
locationOne: '/var/www/html/site/wp-content'
},
develop: {
locationDevOne: '/var/www/html/site/wp-content'
}
},
backups: {
MAX_FILES: 10,
TYPE: 'save',
SRC: {
production: '/home/temp',
develop: '/home/dev/temp'
}
},
log: {
messages: {
'exit': 'message',
'wordpress-start': 'message',
'mysql-start': 'message'
}
}
}Index application
const config = require('./config')
const DumpClass = require('mysql-wordpress-dump').dump
const dump = new DumpClass(config)
dump.startDump()
process.on('exit', () => {
console.log(config['log']['messages']['exit'])
})How do I install, create or edit my own cron job?
To edit or create your own crontab file, type the following command at the UNIX / Linux shell prompt:
$ export EDITOR=nano (optional)
$ crontab -eDo I have to restart cron after changing the crontable file?
No. Cron will examine the modification time on all crontabs and reload those which have changed. Cron does not need to be restarted whenever a crontab file is modified.
Syntax of crontab (field description)
The syntax is:
1 2 3 4 5 /path/to/command arg1 arg2Where,
- 1: Minute (0-59)
- 2: Hours (0-23)
- 3: Day (0-31)
- 4: Month (0-12 12 == December)
- 5: Day of the week(0-7 7 or 0 == sunday)
- /path/to/command – Script or command name to schedule
Easy to remember format:
* * * * * command to be executed
- - - - -
| | | | |
| | | | ----- Day of week (0 - 7) (Sunday=0 or 7)
| | | ------- Month (1 - 12)
| | --------- Day of month (1 - 31)
| ----------- Hour (0 - 23)
------------- Minute (0 - 59)Create CronTab Script
Set the task execution time
Go to Crontab Guru.
Get Node install localtion
Write the following command in the terminal:
$ which nodeGet application location in the system
Enter the following command in the application folder:
$ pwdAdd Backup Type (MySQL Or Wordpress)
If you work with environment variables, you should only set the value BACKUP_ENV to mysql OR wordpress.
This value is required in the command line if you are not working with environment variables. Add mysql OR wordpress after the app location.
For Example:
1 2 3 4 5 /path/to/node /path/to/app/file.js mysqlAdd Execution environment
If you work with environment variables, you should only set the value NODE_ENV to develop OR production.
By default the value is production, so you can skip entering this value if you work from a production server.
IMPORTANT: If you work from a development server and you are not working with environment variables, this value is necessary in the command line, otherwise you will be working with the production values. Add develop after the backup type.
Develop Example (Without NODE_ENV):
1 2 3 4 5 /path/to/node /path/to/app/file.js mysql developDevelop Example (With NODE_ENV = develop):
1 2 3 4 5 /path/to/node /path/to/app/file.js mysqlProduction Example (With or without NODE_ENV = production):
1 2 3 4 5 /path/to/node /path/to/app/file.js mysqlAdd output file for application logs (Optional)
If you want to keep a file for the executions of the application you must add the following to the end of crontab script
1 2 3 4 5 /path/to/node /path/to/app/filefile.js mysql develop >> /path/to/logs/log-file.log 2>&1Full Example
* * * * * ${which node} ${pwd-application}/${filename}.js ${backup-type} ${env} >> ${pwd-logs-location}/${log-filename}.log 2>&1Full Example Without Crontab
node ${filename}.js ${backup-type} ${env}