Skip to content

Latest commit

 

History

History
76 lines (48 loc) · 2.39 KB

README.md

File metadata and controls

76 lines (48 loc) · 2.39 KB

sre-wp-pull

Creative Commons Site Reliability Engineering WordPress Data Pull

⚠️ Destroys and replaces destination data

Code of Conduct

CODE_OF_CONDUCT.md:

The Creative Commons team is committed to fostering a welcoming community. This project and all other Creative Commons open source projects are governed by our Code of Conduct. Please report unacceptable behavior to conduct@creativecommons.org per our reporting guidelines.

Contributing

See CONTRIBUTING.md.

To Do

  • WordPress Multisite rename
  • Additional testing/validation

Assumptions

  1. Destination web hosting and WordPress are configured independently (ex. by SaltStack)
    • wp-config.php is already setup
    • user is a member of www-data
    • Wp-CLI is installed on the destination host
  2. WordPress source data was created using /states/wordpress/files/backup_wordpress.sh found in the creativecommons/sre-salt-prime repository.

Use

  1. Optionally, run backup_wordpress.sh on the source host
  2. Clone this repository
  3. Make a copy of one of the appropriate config_examples/
  4. Execute script with config file as only argument. For example: 
    ./wp-pull.sh chapters__stage

Alternatives

(Only documenting CLI utitilities here. There are also many WordPress plugins devoted to migrating, mirroring, and syncing.)

  • jplew/SyncDB: Bash script meant to take the tedium out of deploying and updating database-driven (eg Wordpress) websites. It rapidly synchronizes local and remote versions of a MySQL database, performs the necessary search and replace queries, then synchronizes all your uploads/binaries.

License