Download the PHP package rmh-media/phpnats without Composer
On this page you can find all versions of the php package rmh-media/phpnats. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
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 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.
Informations about the package phpnats
phpnats
Introduction
A PHP client for the NATS messaging system.
Requirements
- php 5.6+
- gnatsd
Usage
Installation
Let's start by downloading composer into our project dir:
Now let's tell composer about our project's dependancies, in this case, PHPNats. The way we do this is by creating a composer.json file, and placing it in the root folder of our project, right next to composer.phar
Let's let Composer work its magic:
Composer will download all the dependencies defined in composer.json, and prepare all the files needed to autoload them.
Basic Usage
Encoded Connections
Developer's Information
Tests
Tests are in the tests folder.
To run them, you need PHPUnit and execute make test-tdd.
We also have a BDD test suite under the spec folder.
To run the suite, you need PHPSpec and execute make test-bdd.
You can also execute the all suites ( TDD + BDD ) with make test.
Code Quality
We are using PHP Code Sniffer to ensure our code follow an high quality standard.
To perform an analysis of the code execute make lint.
There is currently three steps when we lint our code:
- First we lint with php itself
php -l - Then we lint with PSR2 standard
- And finally we lint with a custom ruleset.xml that checks dockblocks and different performance tips.
Creators
Raül Pérez
License
MIT, see LICENSE
