A WP-CLI based project sharing tool for WordPress. Replaces WP Snapshots.
- Overview
- Why Replace the Old WP Snapshots?
- Getting Started
- Usage
- Identity Access Management and Security
- PII
- Troubleshooting
- Changelog
- Contributing
- Support Level
Snapshots is a project-sharing tool for WordPress. Operated via the command line with WP CLI, this tool empowers developers to easily push snapshots of projects into the cloud for sharing with team members. Team members can pull snapshots, either creating new WordPress development environments or into existing installs such that everything "just works." No more downloading files, matching WordPress versions, SQL dumps, fixing table prefixes, running search/replace commands, etc. Snapshots even works with multisite.
Snapshots stores snapshots in a centralized repository (AWS). Users set up Snapshots with their team's AWS credentials. Users can then push, pull, and search for snapshots. When a user pushes a snapshot, an instance of their current environment (wp-content/, database, etc.) is pushed to AWS and associated with a particular project slug. When a snapshot is pulled, files are pulled from the cloud either by creating a new WordPress install with the pulled database or by replacing wp-content/ and intelligently merging the database. Snapshots will ensure your local version of WordPress matches the snapshot.
A snapshot can contain files, the database, or both. Snapshot files (wp-content/) and WordPress database tables are stored in Amazon S3. General snapshot meta data is stored in Amazon DynamoDB.
The old WP Snapshots was built as a standalone PHP script. This made it difficult to use and install on different environments. The new Snapshots is built as a WP-CLI command making it much more flexible.
Follow the steps below to set up and use Snapshots.
Snapshots is a WP CLI package. An environment with WP CLI enabled is required, and it's highly recommended you run Snapshots from WITHIN your dev environment. For Local, this means opening a shell for one of your projects.
The recommended method for installing the package is directly from the GitHub repository:
wp package install 10up/snapshots:"^1.0.0"The @stable version constraint will install the latest released version.
Alternatively, you can download the package as a zip file from the GitHub repository and install it locally:
wp package install /path/to/snapshots.zipNote: PHP 7.3+ is required.
You must set up your AWS credentials in your local environment. Option 1 is the preferred method.
Create a ~/.aws/credentials file with the following contents (credentials file cannot have an extension):
[default]
aws_access_key_id = <your-access-key-id>
aws_secret_access_key = <your-secret-access-key>Depending on your setup, you may need to create the ~/.aws directory and the credentials file inside of your local environment.
More information in AWS documentation.
Set the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables. See the AWS docs for more information.
You have to configure Snapshots to use a repository. Run the following command:
wp snapshots configure 10up
Make sure to associate Snapshots with the correct AWS profile.
Snapshots revolves around pushing, pulling, and searching for snapshots. Any WordPress installation can be pushed. To pull, all you need is a working WordPress installation with this plugin installed and active.
Documentation for each operation is below.
Snapshots relies on AWS to store files and data. As such, you need to connect to a repository hosted on AWS. Each command supports a --repository argument to tell the script which AWS repository to use, but to bypass requiring that argument on every command, you can store the setting using the command below. After you have done so, Snapshots will use the first repository stored in your configuration by default.
wp snapshots configure [--region=<region>] [--profile=<profile>] [--user_name=<user_name>] [--user_email=<user_email>] [--role_arn=<role_arn>]
Show Arguments
<repository>
The name of the repository to configure.
[--region=<region>]
The AWS region to use. Defaults to us-west-1.
---
default: us-west-1
---
[--user_name=<user_name>]
The username to use. If it's not provided, user will be prompted for it.
[--profile=<profile>]
AWS profile.
[--user_email=<user_email>]
The user email to use. If it's not provided, user will be prompted for it.
[--role_arn=<role_arn>]
Role ARN for AWS. Probably don't need this.
wp snapshots configure 10up
wp snapshots configure 10up --region=us-west-1 --user_name="John Doe" [email protected]
If Snapshots has not been set up for your team/company, you'll need to create the Snapshots repository. If a repository has already been created, this command will do nothing. Note that you must have permissions to create DynamoDB tables and S3 buckets in order to create the repository.
wp snapshots create-repository [--region=<region>] [--profile=<profile>]
Show Arguments
<repository>
The repository to create
[--region=<region>]
The region to create the repository in
---
default: us-west-1
---
[--profile=<profile>]
The AWS profile to use
---
default: default
---
This command pushes a snapshot of a WordPress install to the repository. When finished, the command will return a snapshot ID that you can pass to team members. When pushing a snapshot, you can include files and/or the database.
Snapshots scrubs all user information including names, emails, and passwords.
Pushing a snapshot will not replace older snapshots with the same name. Each time you push, a new copy is created. Old snapshots no longer needed can be removed from AWS with the delete command (see below).
--small will take 250 posts from each post type along with the associated terms and post meta and delete the rest of the data. This will modify your local database, so be careful.
wp snapshots push [<snapshot_id>] [--repository=<repository>] [--exclude=<exclude>] [--slug=<slug>] [--description=<description>] [--wp_version=<wp_version>] [--author_name=<author_name>] [--author_email=<author_email>] [--exclude_uploads] [--small] [--include_files] [--include_db]
Show Arguments
<snapshot_id>
ID of local snapshot to push.
[--repository=<repository>]
Repository to use.
---
default: 10up
---
[--exclude=<exclude>]
Exclude a file or directory from the snapshot. Enter a comma-separated list of files or directories to exclude, relative to the WP content directory.
---
default: ""
---
[--slug=<slug>]
Project slug for snapshot.
---
default: ""
---
[--description=<description>]
Description of snapshot.
---
default: ""
---
[--wp_version=<wp_version>]
Override the WordPress version.
---
default: ""
---
[--author_name=<author_name>]
Snapshot creator name.
---
default: ""
---
[--author_email=<author_email>]
Snapshot creator email.
---
default: ""
---
[--exclude_uploads]
Exclude uploads from pushed snapshot.
---
default: false
---
[--small]
Trim data and files to create a small snapshot. Note that this action will modify your local.
---
default: false
---
[--include_files]
Include files in snapshot.
---
default: true
---
[--include_db]
Include database in snapshot.
---
default: true
---
This command pulls an existing snapshot from the repository into your current WordPress installation, replacing your database and/or wp-content directory entirely. The command will interactively prompt you to map URLs to be search and replaced. If the snapshot is a multisite, you will have to map URLs interactively for each blog in the network. This command will also (optionally) match your current version of WordPress with the snapshot.
After pulling, you can log in as admin with the user wpsnapshots, password password.
wp snapshots pull <snapshot_id> [--repository=<repository>] [--skip_table_search_replace=<skip_table_search_replace>] [--site_mapping=<site_mapping>] [--main_domain=<main_domain>] [--confirm] [--confirm_wp_download] [--confirm_config_create] [--confirm_wp_version_change] [--confirm_ms_constant_update] [--overwrite_local_copy] [--include_files] [--include_db]
Show Arguments
<snapshot_id>
Snapshot ID to pull.
[--repository=<repository>]
Repository to use.
[--skip_table_search_replace=<skip_table_search_replace>]
Skip search and replacing specific tables. Enter a comma-separated list, leaving out the table prefix.
---
default: ""
---
[--site_mapping=<site_mapping>]
JSON or path to site mapping file.
[--main_domain=<main_domain>]
Main domain for multisite snapshots.
[--confirm]
Confirm pull operation.
---
default: false
---
[--confirm_wp_download]
Confirm WordPress download.
---
default: false
---
[--confirm_config_create]
Confirm wp-config.php creation.
---
default: false
---
[--confirm_wp_version_change]
Confirm WordPress version change.
---
default: false
---
[--confirm_ms_constant_update]
Confirm multisite constant update.
---
default: false
---
[--overwrite_local_copy]
Overwrite local copy of snapshot.
---
default: false
---
[--include_files]
Include files in snapshot.
---
default: false
---
[--include_db]
Include database in snapshot.
---
default: false
---
This command searches the repository for snapshots. <search_text> will be compared against project names and authors. Multiple queries can be used to search snapshots in different projects. Searching for "*" will return all snapshots.
wp snapshots search <search_text> [--repository=<repository>] [--format=<format>]
Show Arguments
<search_text>
Text to search against snapshots. If multiple queries are used, they must match exactly to project names or snapshot ids.
[--repository=\<repository\>]
The repository to search in. Defaults to the first repository set in the config file.
[--format=\<format\>]
Render output in a particular format. Available options: table and json. Defaults to table.
This command deletes a snapshot from the remote repository. If you have the snapshot cached locally, your cached copy will not be deleted. (Local copies can be deleted manually within the ~/.wpsnapshots directory.)
wp snapshots delete <snapshot_id> [--repository=<repository>]
Show Arguments
<snapshot_id>
Snapshot ID to pull.
[--repository=<repository>]
Repository to use.
The create command performs most of the same operations as push, but it does not push the generated files and/or database export to AWS. It creates a snapshot locally and stores it your the ~/.wpsnapshots directory. It can subsequently be pulled into any local environment on your machine. This is useful if you want to create snapshots for your own development purposes but don't need to share with others.
wp snapshots create [--repository=<repository>] [--exclude=<exclude>] [--slug=<slug>] [--description=<description>] [--wp_version=<wp_version>] [--author_name=<author_name>] [--author_email=<author_email>] [--exclude_uploads] [--small] [--include_files] [--include_db]
Show Arguments
[--repository=<repository>]
Repository to use.
---
default: 10up
---
[--exclude=<exclude>]
Exclude a file or directory from the snapshot. Enter a comma-separated list of files or directories to exclude, relative to the WP content directory.
---
default: ""
---
[--slug=<slug>]
Project slug for snapshot.
---
default: ""
---
[--description=<description>]
Description of snapshot.
---
default: ""
---
[--wp_version=<wp_version>]
Override the WordPress version.
---
default: ""
---
[--author_name=<author_name>]
Snapshot creator name.
---
default: ""
---
[--author_email=<author_email>]
Snapshot creator email.
---
default: ""
---
[--exclude_uploads]
Exclude uploads from pushed snapshot.
---
default: false
---
[--small]
Trim data and files to create a small snapshot. Note that this action will modify your local.
---
default: false
---
[--include_files]
Include files in snapshot.
---
default: true
---
[--include_db]
Include database in snapshot.
---
default: true
---
This command downloads a snapshot from the remote repository and stores it in the ~/.wpsnapshots directory. It will not pull the data or files into your local environment. If you subsequently run the pull command with the downloaded snapshot ID, the data and/or files will be pulled into your local environment without requiring a new download.
wp snapshots download <snapshot_id> [--repository=<repository>] [--include_files] [--include_db]
Show Arguments
<snapshot_id>
Snapshot ID to download.
[--repository=<repository>]
Repository to use.
[--include_files]
Include files in the download.
---
default: true
---
[--include_db]
Include database in the download.
---
default: true
---
Snapshots is intended to store development environments. It was not meant to be a secure solution to store sensitive production data in the cloud.
Snapshots relies on AWS for access management. Each snapshot is associated with a project slug. Using AWS IAM, specific users can be restricted to specific projects. It is your responsibility to ensure your AWS cloud environment is properly secured.
Snapshots automatically scrubs user information when creating a snapshot. Scrubbed data only includes standard WordPress data e.g. user name, passwords, some user meta, etc. Certain plugins or custom code may store PII elsewhere. It is strongly recommended you review your project for PII (personal identifable information) before pushing snapshots to AWS.
-
wp snapshots push or pull is crashing.
A fatal error is most likely occuring when bootstrapping WordPress. Look at your error log to see what's happening. Often this happens because of a missing PHP class (Memcached) which is a result of not running Snapshots inside your environment (container or VM).
A complete listing of all notable changes to the project are documented in CHANGELOG.md.
Please read CODE_OF_CONDUCT.md for details on our code of conduct, CONTRIBUTING.md for details on the process for submitting pull requests to us, and CREDITS.md for a listing of maintainers of, contributors to, and libraries used by the 10up Block Library.
Beta: This project is quite new and we're not sure what our ongoing support level for this will be. Bug reports, feature requests, questions, and pull requests are welcome. If you like this project please let us know, but be cautious using this in a Production environment!
