Confluence-Sync
Two scripts--one for prod and one for dev/staging. Keeps dev/staging up-to-date with prod.
Dependencies
Script assumes you have already setup an ssh key to the staging from prod and have configured your server to not ask for mysql password. All folders on staging/dev should be created before you run the script for the first time.
Description
These two scripts are placed on corresponding prod and dev/staging servers. The production one shuts down the Confluence service, does a mySQL dump, and then rsyncs over the dump and main directories to a backup directory and then turns the service back on. The directories and dump are then scp-d over to dev/staging. The staging script shuts down the Confluence service, then copies the directories from prod to the corresponding locations. SQL entries are modified to account for staging variables, then the service is turned back on.
Usage
Run jobs via cronjob. Make sure the prod finishes before you have the dev/staging set to run
For example, this is what my crontab looks like for prod:
0 1 * * * /opt/confluence-sync/confluence-prod.sh >> /opt/confluence-sync/LOG/confluence-sync.log 2>&1
And this is what I run on the staging/dev server:
0 2 * * * /opt/confluence-sync/confluence-staging.sh >> /opt/confluence-sync/LOG/confluence-sync.log 2>&1
The script clears the logs before every run because rsync-ing all those files and folders fills it up quickly.