Download the PHP package paloma/client-bundle without Composer
On this page you can find all versions of the php package paloma/client-bundle. 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 client-bundle
Paloma Client Symfony Bundle
A Symfony bundle for easy integration of the paloma/shop-client package into a Symfony application.
Features:
- Configure your Paloma shop client within a Symfony app configuration
- Paloma client factory and convenience service definition
- Integration into the Symfony web profiler
Usage
To get the default Paloma client (read below what that means):
Instead of requesting the default client "at runtime" over the
$cotainer->get() method you can also make use of Symfony's auto wiring feature
by using the DefaultPalomaClient class:
To get the client factory in order to get other clients than the default one:
Installation
Add the bundle to your application:
Then add add it to your AppKernel.php:
Configuration
Channels and Locales
Paloma is built around the notion of channels. One Paloma setup may consist of many different channels. Good examples of channels are "country" or "tenant" (in a multi tenant system). Each Paloma API endpoint is prefixed by the channel (see Paloma API docs for more information). In addition to channels most API endpoints also take a prefix for the locale of the request. Paloma itself cannot determine the correct channel or locale and it is the frontend application's job to define that.
This job is normally done by applying some URL scheme to the frontend
application, like for example
https://<tenant>.myclient.com/<country>/<language>/<path>. In this example the
resulting Paloma channel might be <tenant>_<country> and locale <language>.
The important part is that channels are project specific and can change in
syntax and semantics.
For that reason it has to be solved again in every application.
The standard way to solve this is to install a request listener which analyzes the incoming URL and determines the channel and locale from that URL. It then sets the default channel using:
After this no other code in the application needs to care about channels or locales. This should handle most common use cases as the need to address multiple channels or locales within the same request is rare.
Paloma trace ID
Paloma allows for the specification of a trace ID alongside every request. This helps to correlate requests observed on Paloma and the client application with each other.
The Paloma trace ID has to be a string which is exactly 8 characters long and consists of only lower case characters a-z and digits 0-9.
It is possible to set this trace ID within the ClientFactory such that it will
be added to every request to Paloma which is sent through a client created by
that factory. A convenient location to set the trace ID is probably in the same
area as the default channel and locale is set.
It can be done like this:
All versions of client-bundle with dependencies
paloma/shop-client Version ^2.6
symfony/monolog-bundle Version >=3.0.2
symfony/framework-bundle Version >=3.3,<5.0