Download the PHP package efrane/tinkr without Composer

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

tinkr

tinkr is a testbed console thing for PHP. one day I will come up with a better explanation. for now, just know that you can do this:

Usage

If called without any arguments, tinkr essentially behaves like it's underlying PsySh, with the exception that you end up in a sandboxed environment. But of course, the actual benefit of tinkr is passing composer package names for quickly testing them without having to manually require-write-script-run the test.

Export

Tinkr sessions are by default temporary because they are just meant for quick testing without all the hassle of composer require and autoloading and stuff. If you need the things saved, it's possible to export a session to a permanent location by calling the export command in the session. This will write the session to a sub-directory your current dir. If you want a specific storage path, you can pass that as an argument, e.g. export ~/my_tinkr_session.

Exported sessions will not be overridden unless you run the command as export --force.

In the future, tinkr will try to generate a PHP script from the command history, for now, the export just contains the bare environment, which, however, allows for reopening in tinkr with $ tinkr --path your-exported-tinkr-session.

Installation

via composer:

Don't forget to add your .composer/vendor/bin to your $PATH

License: MIT


All versions of tinkr with dependencies

PHP Build Version
Package Version
Requires psy/psysh Version ^0.5.2
symfony/console Version ^2.7
symfony/process Version ^2.7
symfony/filesystem Version ^2.7
composer/composer Version *
nesbot/carbon Version dev-master
illuminate/container Version ^5.1
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 efrane/tinkr contains the following files

Loading the files please wait ....