dev-master
9999999-devA PHP client for communicating with Asink
The Requires
- php >=5.4.0
- guzzlehttp/guzzle 5.0.*@dev
- illuminate/support ~5.0
The Development Requires
library client groundsix asink
A PHP client for communicating with Asink
A simple PHP client library for Asink., (*1)
$ asink server [asink] listening on :3000
Install package via composer, (*2)
"require": { "asink/asink-php": "dev-master" }
Add the service provider in app/config/app.php
, (*3)
'providers' => [ 'Asink\Component\AsinkServiceProvider' ];
And you can also add the Facade if you'd like, (*4)
'aliases' => [ 'Asink' => 'Asink\Component\AsinkFacade' ];
With Asink installed and running, in Laravel you can run command like so:, (*5)
<?php Route::get('/asink-test', function() { Asink::addTask('make-directory', array( "command" => "mkdir", "args" => [ "my-dir-1", "my-dir-2" ] )); Asink::start(); });
<?php require("vendor/autoload.php"); $client = new Asink\Component\Client(); $client->addTask("make-directory", array( "command" => "mkdir", "args" => [ "my-dir-1", "my-dir-2" ] )); $client->start();
There are various options and things you can do in terms of organising your commands and in which way they are ran. Here are the docs for Asink which show what options can be used., (*6)
$client->addTask("do-ls", array( "command" => "mkdir", // The root command "args" => [ // Add command arguments as an array "my-dir-1", "my-dir-2" ], "count" => [1, 1], // How many times do we want to run it? "dir" => "~", // Which directory should it be ran in? "group" => "stuff", // Should it be ran as part of a group? "require" => "do-ls" // Do we require anything to run first? )); $client->addTask("do-ls", array( "command" => "ls" )); $client->start();
MIT, (*7)
, (*8)
A PHP client for communicating with Asink
library client groundsix asink