Download the PHP package pointblue/deployer without Composer

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

Informations about the package deployer

Point Blue Deployer

Supporting deployer tasks

Install

This will install the package globally

composer global require pointblue/deployer

This package is available from packagist - https://packagist.org/packages/pointblue/deployer

Configuration

  1. Edit the php.ini for your command line environment at /etc/php/VERSION/cli/php.ini where VERSION is something like 5.6 or 7.2.
    Find out your php cli version with php --version
  2. Find composer's global path with composer config --list --global and find the property [home]. Append /vendor to this property and use this path for the next step.
  3. Update include_path by appending the global composer's vendor path to the end of the string as :/home/user/.config/composer/vendor and save the file.
    Example: include_path = ".:/usr/share/php:/home/ubuntu/.config/composer/vendor".
  4. Create a file named .slack_webhook_url in the home folder of the user that will be running the composer script. The contents of the file should be the url of the slack webhook that will be posted to on deploy completetion. This will enable build notifications to be posted to that url. If this is not done, notifications will not be sent. The recommended permission for the file is 600 (chmod 600 .slack_webhook_url).

Use

deployer.php

To use the deployer tasks, just require the tasks in your deployer.php file at the top, but after other required files.

Example:

Next, add the hooks need for the tasks to run:

cli

To test commands without running them on the target server, use the --pb-test option.

Example:

dep deploy:symlink_envs aws --pb-test -vvv

This will run the deploy:symlink_envs task with the aws stage settings from the servers.yml file and print the symlink commands in the console instead of running them on the server. This will let you test your configurations before deploying.

servers.yml variables

Some additional variables can be added to your hosts definition in the servers.yml file.

env_symlinks - see deploy:symlink_envs in common-tasks.php
update_autoload_classmap - see deploy:update_autoload_classmap in common-tasks.php

Development

Notes on developing this project.

Symlink to global composer path (optional)

It's best to symlink this project from your global composer path. This way your edits can be tested right away.

This is how I used a symlink on my system:

This allows the require 'pointblue/deployer/common-tasks.php'; line in deploy.php to refer to the pointblue/deployer repo I cloned. Now my edits are under source control and can be tested lived.

Use debug tasks

You can run debug tasks from you machine to see how individual functions behave and drop break points.

Reference

Please see the source code for task names and their use

All versions of deployer with dependencies

PHP Build Version
Package Version
Requires ext-json Version *
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 pointblue/deployer contains the following files

Loading the files please wait ....