Download the PHP package gaambo/deployer-wordpress without Composer

On this page you can find all versions of the php package gaambo/deployer-wordpress. 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?

Example code of gaambo/deployer-wordpress

Informations about the package deployer-wordpress

Deployer WordPress Recipes

Deployer tasks and recipes for deploying WordPress sites. Supports simple rsync deployments, custom theme/plugin builds, and complex setups including Bedrock and multisite.

Table Of Contents

Installation

  1. composer require gaambo/deployer-wordpress --dev
  2. Copy example files from examples/simple/ or examples/bedrock/ to your project root
  3. Customize deploy.php and deploy.yml:
  1. Test on staging first, then deploy to production 🚀

Requirements

Optional (auto-installed on remote if missing):

Configuration

Example recipes (in examples/) provide configuration starting points. The library works with any WordPress setup ( vanilla, Composer, subdirectory, Bedrock, multisite) by making all paths and directories configurable. Check the example recipes and task source files for available options.

Localhost context

Version 4 introduces a proper Localhost context. This ensures that when tasks run on your local machine (like building assets or backing up the local database), they use configuration values specifically defined for localhost, rather than falling back to global or remote values.

Configure localhost in deploy.php:

The Localhost utility class (Gaambo\DeployerWordpress\Localhost) handles switching context automatically in tasks.

deploy_path is the project root and is used for private data such as relative database dump paths. current_path is the WordPress root. The previous project_path example setting was unused and has been removed.

wp-config.php (Recommendation)

Keep wp-config.php in git and deploy it. Extract environment-specific config (database credentials, WP_DEBUG) into wp-config-local.php, which should be gitignored and created manually on each host. Require it from wp-config.php:

Rsync filters

The default rsync config uses .deployfilter files for per-directory filtering. Place a .deployfilter file in your theme/plugin to exclude development files:

This prevents any development files/development tools from syncing. I strongly recommend you put something like this in your custom theme and mu-plugins or overwrite any of the themes/filter or mu-plugins/filter configurations.

Tasks

Tasks are in the tasks/ directory. Run dep list to see all available tasks. See task source files for configuration options.

Database Tasks (tasks/database.php)

Multisite support

For multisite installations, set wp/multisite to true to enable network-wide search-replace during database sync:

Packages system (tasks/packages.php)

Manage custom themes, plugins, and mu-plugins with individual build configs:

Tasks:

Other Task Categories

File Tasks (tasks/files.php)

WordPress Core (tasks/wp.php)

Languages (tasks/languages.php)

Uploads (tasks/uploads.php)

Legacy Tasks (use packages instead)

Recipes

v4 uses current_path for rsync-based deployments. Symlinked releases are still possible but not the default.

recipes/simple.php - Standard WordPress. Rsyncs directly to current_path. Recommended for most projects.

recipes/bedrock.php - Roots Bedrock projects with appropriate structure and environment handling.

Changelog

See CHANGELOG.md.

Contributing

Issues, feature requests, and pull requests welcome at GitHub. Code follows PSR-2 and Deployer best practices.

Testing

The library includes a comprehensive test suite with unit, integration, and functional tests.

The library supports both Deployer v7 and v8. Test against both before submitting (note: Deployer v7 requires PHP 8.2 or 8.3 — it is incompatible with PHP 8.4+):

All versions of deployer-wordpress with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
deployer/deployer Version ^7.3
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 gaambo/deployer-wordpress contains the following files

Loading the files please wait ...