Download the PHP package vimeo/ablincoln without Composer

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

ABLincoln Latest Stable Version Build Status

ABLincoln is a PHP-based implementation of Facebook's PlanOut, a framework for online field experimentation. ABLincoln makes it easy to deploy and maintain sophisticated randomized experiments and to quickly iterate on these experiments, while satisfying the constraints of large-scale Internet services with many users.

Developers integrate ABLincoln by defining experiments that detail how inputs (e.g. users, cookie IDs) should get mapped onto conditions. To set up an experiment randomizing both the text and color of a button, you would create a class like this:

Then, in the application code, you query the Experiment object to find out what values the current user should be mapped onto:

Querying the experiment parameters automatically generates an exposure log that we can direct to a location of our choice:

The basic SimpleExperiment class logs to a local file by default. More advanced behavior, such as Vimeo's methodology described below, can easily be introduced to better integrate with your existing logging stack.

Installation

ABLincoln is maintained as an independent PHP Composer package hosted on Packagist. Include it in in your composer.json file for nice autoloading and dependency management:

Comparison with the PlanOut Reference Implementation

ABLincoln and the original Python release of PlanOut are very similar in both functionality and usage. Both packages implement abstract and concrete versions of the Experiment and Namespace classes, parameter overrides to facilitate testing, exposure logging systems, and various random assignment operators tested and confirmed to produce identical outputs.

Notable differences between the two releases currently include:

Usage in Production Environments

ABLincoln was ported and designed with scalability in mind. Here are a couple ways that Vimeo has chosen to extend it to meet the needs of our testing process:

Application to an Existing Logging Stack

The Experiment logging traits provided with this port make it easy to log exposure data in the most convenient way possible for your existing stack. A quick implementation of the plug-and-play FileLoggerTrait andtail -f of the log file is all you need to monitor parameter exposures in real-time. Alternatively, the PSRLoggerTrait allows more customizable integration with existing PSR-compliant logging code. Here at Vimeo, we use a basic Monolog Handler to enforce PSR-3 compliance and allow PlanOut to talk nicely to our existing logging infrastructure.

URL Overrides

ABLincoln already supports parameter overrides for quickly examining the effects of difficult-to-test experiments. A simple way to integrate this behavior with a live site is to pass overrides into your endpoint as a query parameter:

Then it's a relatively simple task to parse the overrides from the query and pass them into the PHP Experiment API override methods after instantiation.

Thanks

PlanOut, the software from which ABLincoln was ported, was originally developed by Eytan Bakshy, Dean Eckles, and Michael S. Bernstein, and is currently maintained by Eytan Bakshy at Facebook. Learn more about good practice in large-scale testing by reading their paper, Designing and Deploying Online Field Experiments.


All versions of ablincoln with dependencies

PHP Build Version
Package Version
Requires php Version >=5.4.0
psr/log Version ~1.0
monolog/monolog Version ~1.0
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 vimeo/ablincoln contains the following files

Loading the files please wait ....