Download the PHP package flytachi/winter-logger without Composer
On this page you can find all versions of the php package flytachi/winter-logger. 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 winter-logger
Winter Logger
A PSR-3 logger that stays correct when one process serves many requests at once. It wraps Monolog with per-unit-of-work context isolation, Spring Boot-style output and a Java-style static factory, so the same logging code behaves the same under FPM, CLI and Swoole.
The library is infrastructure-agnostic: it never reads env vars and never detects Docker, the SAPI or Swoole. The framework that boots it builds the channel config and passes it in — which is what keeps the package testable and usable outside Winter.
📖 Documentation · Quick start · API reference · Channel config
Installation
Requires PHP 8.3+ and psr/log ^3.0. monolog/monolog ^3.5 is a suggestion rather
than a dependency — install without it and every channel resolves to a NullLogger instead
of failing. ext-swoole is needed only for CoroutineContext.
Quick start
Build a manager with your channels and hand it to the factory once at bootstrap:
Then log from anywhere:
The last line goes to cli, which sits at Debug — a debug() call on the default http
channel above would have been filtered out, since that one is configured at Info.
What you get
- Context that cannot leak — fields set once per request appear in every record, and live in the coroutine under Swoole, in the process under FPM and CLI.
- Per-class loggers —
LoggerFactory::getLogger(self::class)names the record after the class that wrote it, cached per class. - Bound context —
withContext([...])returns a logger carrying those fields into every later call, without mutating the original. - Five outputs —
stdout,stderr,syslog, rotatingfile, andnullfor tests. - Two formats — a readable line for humans, JSON for collectors, with optional ANSI colour on the line.
- Sensitive-value masking — passwords and tokens are replaced before a record is written, not after it is read.
- Survives a closed pipe — a
SIGPIPE-safe stream handler, so a reader that went away cannot take the process down. - Monolog optional — absent, everything degrades to
NullLogger; logging never prevents a boot.
Request-scoped context
Set the fields once at the start of the unit of work and every record picks them up:
Under Swoole, pass CoroutineContext instead of ProcessContext and each concurrent
request gets its own bag — see
Context isolation.
Documentation
The user-facing documentation lives at winterframe.net/packages/logger (the link picks your language; RU and EN are both complete).
Start here
| Page | What it answers |
|---|---|
| Introduction | What the package is, and what it adds to Monolog |
| Installation | Requirements, optional Monolog, Swoole |
| Quick start | Bootstrap, first channel, first record |
| Mental model | Storage, manager, factory, facade — who does what |
Guides
| Page | What it answers |
|---|---|
| Framework integration | Wiring it into an application's entry point |
| Request context | Attaching fields to every record of a request |
| Swoole coroutines | Keeping context isolated under concurrency |
| Dynamic channels | Adding a channel after bootstrap |
| Masking sensitive data | Keeping secrets out of the log |
Reference
| Page | What it answers |
|---|---|
| API reference | Every class and method |
| Channel config | Each config key, output target and format |
| Log format | What each segment of a line means |
Deep dive
| Page | What it answers |
|---|---|
| Log record lifecycle | What happens between the call and the write |
| Context isolation | Why storage belongs to a unit of work |
| Output and broken pipe | Surviving a reader that went away |
| Monolog optional | What degrades without it, and how quietly |
Classes in this package carry an @link to their page, so the same documentation is one
click away from your IDE.
Contributing
Internal technical notes — exact contracts, invariants, and the reasoning behind decisions
that are not obvious from the code — live in docs/. Read that before
changing how a record is built.
License
MIT License. See LICENSE.
