Libraries tagged by tracking code

leibbrand-development/php-docker-client

0 Favers
33 Downloads

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.41) is used. For example, calling `/info` is the same as calling `/v1.41/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download


zim32/symfony-tracing-core

1 Favers
50 Downloads

Symfony OpenTelemetry integration core bundle

Go to Download


kaspiman/symfony-tracing-core

0 Favers
3 Downloads

Symfony OpenTelemetry integration core bundle

Go to Download


orlyapps/laravel-event-tracking

0 Favers
348 Downloads

Event Tracking per Model and with API

Go to Download


coretsia/platform-tracing

0 Favers
2 Downloads

Coretsia tracing runtime package: deterministic W3C traceparent propagation, bounded validation, and Foundation noop fallback.

Go to Download


rukhsar/modelhistory

0 Favers
11 Downloads

Provides tracking of Laravel Models for creating, updating and deleting events

Go to Download


mjanser/dead-code-detector-patchlevel-event-sourcing

0 Favers
5 Downloads

PHPStan extension teaching shipmonk/dead-code-detector about patchlevel/event-sourcing

Go to Download


karimms/model-pulse

0 Favers
0 Downloads

Add collaboration, messaging, and activity tracking to any Eloquent model.

Go to Download


anonimowybanan/model-diff

0 Favers
1 Downloads

Laravel package for tracking and comparing Eloquent model changes

Go to Download


act-training/laravel-model-versions

0 Favers
261 Downloads

A Laravel package for automatic model versioning with selective attribute tracking and restore capabilities

Go to Download


contenir/contenir-tracking-laminas-mvc

0 Favers
3 Downloads

Laminas MVC view helpers for contenir/contenir-tracking: tracking()->head() and tracking()->bodyStart() write a site's tags, Consent Mode first, with the page's CSP nonce.

Go to Download


contenir/tracking-laminas-mvc

0 Favers
0 Downloads

Laminas MVC view helpers for contenir/contenir-tracking: tracking()->head() and tracking()->bodyStart() write a site's tags, Consent Mode first, with the page's CSP nonce.

Go to Download


xcopy/laravel-model-state-transitions

0 Favers
4 Downloads

Manage state transitions for your Laravel models with role-based access control and automatic history tracking.

Go to Download


silvershop-suite/conversion-tracking-google

0 Favers
0 Downloads

Google connector for silvershop-suite/conversion-tracking: GA4 ecommerce events (view_item / add_to_cart / begin_checkout / purchase) via gtag, a Google Ads conversion on purchase, Enhanced Conversions (hashed email, hashed client-side by Google) and Consent Mode v2 inherited from silvershop-suite/cookieconsent.

Go to Download


contenir/contenir-tracking-mezzio

0 Favers
1 Downloads

Mezzio adapter for contenir/contenir-tracking: a shared service whose head() and bodyStart() write a site's tags, Consent Mode first, with the page's CSP nonce, and a tracking() helper for laminas-view layouts.

Go to Download


<< Previous Next >>