Download the PHP package bureaupieper/storee-php-client without Composer
On this page you can find all versions of the php package bureaupieper/storee-php-client. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download bureaupieper/storee-php-client
More information about bureaupieper/storee-php-client
Files in bureaupieper/storee-php-client
Package storee-php-client
Short Description Client for the Store-E REST API
License MIT
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 storee-php-client
Store-E PHP Client 
Store-E is a content(-as-a-service/repository) platform taking care of all your content management needs. Content is delivered through 'Hotspots' and 'Pages' which you can define. Published content comes along with every form of media, which is also delivered through-, automated and managed by Store-E. Bitmaps in multiple formats and resolutions(no restrictions), videos in H.264, MP4, OGV, documents, third party integrations, and much more.
This client enables you to connect your website, enterprise network or social media platforms to our content repository in a matter of hours.
This library supports PSR-3 logging and provides some extra functionality for Monolog. Caching is handled by Stash. HTTP abstraction is handled by Guzzle. You're free to provide your own for any of the dependencies.
Installation
Stand-alone
Symfony users
See the BureauPieper/storee-php-client-bundle for easy integration!
Usage:
Create the configuration container
See the tree for all the possibilities. The container makes sure your provided options are conflict-free.
Instantiate the client
Create the intermediary request object, and fire away.
Content items in a result set are wrapped by ContentResult.php to ease development.
HTTP
A plain GuzzleHttp instance is used by default, checkout Guzzle for more information.
- getlastRequest doesnt work when passing your own client, feel free to add to your own handler stack when passing a client as following:
Caching
Enabled by default with a filesystem driver. See Stash for a wide variety of driver options if you need to setup memcache across multiple nodes for example.
Cache will be refreshed based on the Time-to-renew(ttr) setting, TTL is irrelevant. If the endpoint goes down the platform stays up.
PSR-3 Logging
Can be enabled, if no implementation is provided Monolog will be used with two RotatingFileHandlers. Both INFO and ERR will be be saved to , but it is recommended to pass a monolog instance with some filesystem handlers and setup logrorate yourself.
The mail setup will only work with the default logger instance.
Documentation
W.I.P
Contact
- [email protected] (tech)
- [email protected] (inquiries)
All versions of storee-php-client with dependencies
guzzlehttp/guzzle Version ^6.1
tedivm/stash Version ^0.13.1
symfony/dependency-injection Version ~2.7
symfony/config Version ~2.7
psr/log Version ^1.0