⬡ Lacelium
⌘K
Version 2.x ▾

Dipperlook Overview

Introduction

Dipperlook is the deep utility and infrastructure subsystem of the Lacelium framework. While the core MVC layers handle standard HTTP routing, controllers, and views, Dipperlook provides the industrial-grade tooling required for scalable production applications.

Named after the framework's ability to "look deeper" into application state, Dipperlook houses subsystems for background task automation, high-speed multi-driver caching, file system virtualization, resilient HTTP client communications, internationalization, and end-to-end security safeguards.

The Dipperlook Subsystems

Dipperlook comprises six modular, independently configurable service layers:

1. Dipper Console

A fast, expressive command-line interface based on Symfony Console that provides generators for models, controllers, migrations, and Nexify real-time daemons, along with an execution allow-list system to prevent unauthorized command injection.

2. Cache Engine

A unified caching interface supporting file-based cache, in-memory array cache, Redis, and APCu with automatic TTL expiration, atomic increment/decrement, and tag-based invalidation.

3. File Storage

A powerful filesystem abstraction providing unified drivers for local storage, secure public uploads, and cloud storage adapters (S3, Cloudflare R2, MinIO) with automatic MIME validation.

4. HTTP Client

A fluent, expressive wrapper around Guzzle HTTP that allows you to easily make outbound HTTP requests to communicate with external APIs, microservices, and webhooks with built-in retry policies and error inspection.

5. Localization

Multi-language translation strings, automatic client locale resolution from request headers and sessions, fallback locale chains, and pluralization mechanics.

6. Security Safeguards

Built-in shields against cross-site request forgery (CSRF), cross-site scripting (XSS), SQL injection, strict file upload sanitization, and secure Argon2id password hashing.

Accessing Dipperlook Services

All Dipperlook subsystems are bound into the Lacelium dependency injection container and can be accessed via type-hinted constructor parameters or global helper functions:

use Lacelium\Core\App;

// Accessing via global helper functions
$cache = cache();
$storage = storage();
$http = http();

// Accessing via Container resolution
$cache = App::container()->get(\Lacelium\Core\Cache\CacheManager::class);

Configuration

Each Dipperlook service has its dedicated configuration file located in the config/ directory:

  • config/cache.php: Cache drivers, prefixes, and default store
  • config/filesystems.php: Disks, root paths, and visibility settings
  • config/app.php: Locale, fallback locale, and security encryption keys

Next Steps