Download the PHP package tigron/skeleton-container-control without Composer

On this page you can find all versions of the php package tigron/skeleton-container-control. 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 skeleton-container-control

skeleton-container-control

Description

This library enables the communication with a remote server. The remote server needs to have the skeleton-container package installed.

Installation

Installation via composer:

composer require tigron/skeleton-container-control

Howto

Initialize the service directory

\Skeleton\Container\Control\Config::$service_dir = $some_very_cool_directory;

The following skeleton console commands will be available:

container
 container:deprovision  Deprovision a service from a container
 container:info         Get info of a paired container
 container:list         List all paired containers
 container:pair         Pair with a new container
 container:provision    Provision a container with a new service
 container:rename       Rename a container
 container:unpair       Unpair from a container
service
 service:diff           Show differences between the local and remote service, if any
 service:list           List all known services

To create a service, create a directory structure like this in your service directory:

service_name
├── lib                     # Libraries needed for this service
└── module                  # Contains the module for the service

In the module directory, at least 1 file should be added: index.php. This module will handle all the incoming requests. It is a class that should extend from 'Service_Module'

This is an example of a very basic module:

<?php
/**
 * Dummy module
 *
 * @author Christophe Gosiau <[email protected]>
 * @author Gerry Demaret <[email protected]>
 */

class Web_Module_Index extends Service_Module {

    /**
     * Handle call1
     *
     * @access public
     * @param array $data
     */
    public function handle_call1($data) {
    }
}

After deployment, the remote server can respond to call1. To make a call, use this:

$container = \Skeleton\Container\Control\Container::get_by_name('my_remote_container');
$service = \Skeleton\Container\Control\Service::get_by_name('dummy');
$container_service = $container->get_container_service($service);
$data = [
    'param1' => 'this is a test',
    'param2' => 'This is another test'
];
$container_service->call1($data);

A service by default runs in 'production' mode. This means the calls will be handled by Web_Module_Index. For testing purpose, the environment can be modified to 'debug'. By doing so the calls will be handled by Web_Module_Debug. This is optional but strongly encouraged. When creating the service, make sure both production calls and debug calls are available. To enable debug mode, perform the following calls:

$container = \Skeleton\Container\Control\Container::get_by_name('my_remote_container');
$service = \Skeleton\Container\Control\Service::get_by_name('dummy');
$container_service = $container->get_container_service($service);
$container_service->set_environment('debug');
$data = [
    'param1' => 'this is a test',
    'param2' => 'This is another test'
];
$container_service->call1($data);

All versions of skeleton-container-control with dependencies

PHP Build Version
Package Version
Requires guzzlehttp/guzzle Version ~7
tigron/skeleton-object Version >=0.1.22
tigron/skeleton-database Version >=0.1.6
tigron/skeleton-migrate Version >=0.1.9
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 tigron/skeleton-container-control contains the following files

Loading the files please wait ....