Download the PHP package sourcebroker/deployer-bulk-tasks without Composer

On this page you can find all versions of the php package sourcebroker/deployer-bulk-tasks. 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 deployer-bulk-tasks

! Note - project no longer maintained

deployer-bulk-tasks

|

:local:

What does it do?

This library takes cli commands of any package and makes them available as deployer tasks.

Installation

1) Install package with composer:

composer require sourcebroker/deployer-bulk-tasks

2) Take look at presets in folder vendor/sourcebroker/deployer-bulk-tasks/preset, choose yours and put following line in your deploy.php file, like in this example:

require_once (__DIR__ . '/vendor/sourcebroker/deployer-bulk-tasks/preset/Magento2.php');

3) If you found the right presets then at this point you are done and you can check for new commands with "dep".

4) If you did not find preset then you can add your own config and require BulkTask.php after config like in this example:

set('bulk_tasks', [
    [
        'prefix' => 'magento',
        'binary' => './bin/magento',
        'binary_required' => true,
        'command' => 'list --raw',
        'command_filter' => '',
        'command_fallback' => '
              admin:user:create                         Creates an administrator
              admin:user:unlock                         Unlock Admin Account
              app:config:dump                           Create dump of application
              ...
              ...
              ...
        '
    ],
]);
require('./vendor/sourcebroker/deployer-bulk-tasks/src/BulkTasks.php');

Options

prefix A prefix that will be put before each command from cli to build deployer task name. You can consider that a namespace for deployer tasks. Usually it will be framework name, like "magento", "typo3". See folder with presets for example.

binary Cli application binary.

binary_required If true then the php exception will be thrown if binary is not found.

command A command that together with binary will output raw command list like "php bin/magento list --raw".

command_filter A string to be used in preg_match to filter commands that should be deployer tasks because usually we do not need all commands to be available as deployer tasks. Example "/.database:./".

command_fallback A string that contains commands that you want to be deployer tasks and that are added independent of what will be returned from cli binary.

Commands usage

After installation and configuration you can use all commands of application like in following example from TYPO3 preset:

dep typo3cms:database:updateschema live

If you want to see the output of command then use -vvv switch. Example:

dep typo3:cleanup:deletedrecords live -vvv

If you want to add some option then use "--bulk-task-option" option and put whole option inside. Example:

dep typo3cms:database:updateschema live --bulk-task-option="--schema-update-types=\"*.add\""

Your presets

If you have some new presets for some well known frameworks then please create a PR and I will merge it to master.

Known problems

None.

To-Do list

None.

Changelog

See https://github.com/sourcebroker/deployer-bulk-tasks/blob/master/CHANGELOG.rst

All versions of deployer-bulk-tasks with dependencies

PHP Build Version
Package Version
No informations.
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 sourcebroker/deployer-bulk-tasks contains the following files

Loading the files please wait ....