Download the PHP package opsone/wp-cli-deploy without Composer

On this page you can find all versions of the php package opsone/wp-cli-deploy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package wp-cli-deploy

Project maintainers welcomed

January, 2017

WP-Cli Deploy

Current Version: 1.2.0

Deploys the local WordPress database or uploads directory.

The tool requires defining a set of values in your wp-cli.yml file. The constants should be prefixed with the environment handle which you will use as the first parameter for your desired subcommand. An example configuration for a "dev" environment:

=> wp deploy push dev ...

Not all commands / subcommands require all constants to be defined. To test what a subcommand requires, execute it with a non-existing environment handle. e.g. wp deploy dump dev.

You can define as many constant groups as deployment enviroments you wish to have.

Examples

# Deploy the local db to the staging environment
wp deploy push staging --what=db

# Pull both the production database and uploads
wp deploy pull production --what=db && wp deploy pull production --what=uploads

# Pull both the production themes and plugins
wp deploy pull production --what=themes && wp deploy pull production --what=plugins

# Dump the local db with the siteurl replaced
wp deploy dump production

Configuration Dependecies

Subcommands depend on different constants in order to work. Here's the dependency list:

%%ENV%%_POST_HOOK

You can optionally define a constant with bash code which is called at the end of the subcommand execution.

You can refer to environment variables using placeholders. Some of the available environment variables are:

Example

Here's an example of a DEV_POST_HOOK that posts a message to a hipchat room after a pull or a push is performed using the HipChat REST API (https://github.com/hipchat/hipchat-cli). For pushes, it also clears the cache.

Credits


All versions of wp-cli-deploy with dependencies

PHP Build Version
Package Version
Requires php Version >=5.4
wp-cli/wp-cli Version >=0.14
symfony/yaml Version ~2.7
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package opsone/wp-cli-deploy contains the following files

Loading the files please wait ....