- What is torann/registry used for in a Laravel application?
- It is a lightweight key-value registry for storing application-wide settings and runtime values using a clean get, set, has, and forget API. Values can be backed by an in-memory array, a JSON file, or a database table, and dot notation lets you manage nested configuration keys. It is best treated as a primitive for runtime-editable settings such as maintenance toggles, banners, upload limits, or default locale, not as a full settings or feature-flag platform.
- How do I install torann/registry in Laravel?
- Install it with composer require torann/registry, then publish the package configuration and migration using vendor:publish and run php artisan migrate. On Laravel 5.5 and newer the service provider is auto-discovered, so you do not need to register anything in config/app.php. The Registry facade and the registry() helper resolve automatically once the package is installed.
- Which storage drivers does torann/registry support?
- It ships with three drivers: an in-memory array, a JSON file, and a database table. The array driver is per-request and useful for tests or ephemeral values, while the file and database drivers persist values between requests. You select the driver in the package configuration file.
- Does torann/registry support dot notation for nested keys?
- Yes, get and set calls accept dot-notation keys so you can read and write nested values without managing arrays manually. The API also supports default values on get and existence checks through has-style methods, which keeps call sites simple. This is sufficient for realistic site-wide settings such as onboarding copy arrays or pricing display rules.
- How do I persist registry values in the database with torann/registry?
- Publish the package migration, run php artisan migrate to create the single registry table, and set the driver to database in the published config. After that, set calls write through to the table and survive between requests. The whole setup is three commands: composer require, vendor:publish, and migrate.
- Is torann/registry safe in a multi-node deployment with a load balancer?
- Multi-node cache coherence is the top production risk with this package, because the in-memory cache layer can leave sibling nodes serving stale values after a write. Plan for this explicitly with a cache-clearing strategy, short TTLs, or a central source of truth, and test it behind your actual load balancer. Treat this as the one area where the package's design influences your infrastructure decisions.
- Which Laravel and PHP versions does torann/registry support?
- No formal compatibility matrix is published, so support for current Laravel and PHP versions is an assumption rather than a fact. Gate adoption with an explicit spike on your target version: publish the config, migrate, run one set and one get, clear the cache, and scan logs for PHP 8.2+ deprecation noise. Do not infer compatibility from the fact that it is a Laravel package.
- How does torann/registry compare to spatie/laravel-settings or Laravel Pennant?
- torann/registry is a thin key-value primitive, whereas spatie/laravel-settings provides typed settings classes and Laravel Pennant provides feature flags with targeting and percentage ramps. Use this package for simple site-wide configuration values, and graduate to Pennant when you need per-user targeting or audience segmentation rather than extending the registry. Because the package surface is small, wrapping it behind your own interface makes that eventual migration a refactor instead of a hunt.
- Is torann/registry actively maintained and production ready?
- Dependency health is thin: there is no meaningful community maintenance signal to rely on, so the realistic planning assumption is that your team owns this code, including the possibility of forking or vendoring it. The mitigating factor is that the entire package surface is small enough to read in an afternoon, which caps the downside. Before the second call site exists, build an internal Settings wrapper bound to an interface and forbid direct facade imports elsewhere.
- How do I test torann/registry or clear cached values in Laravel?
- Use the array driver in your test suite so each test starts with a clean in-memory store, and call the forget method to remove keys between assertions. When you change a value in staging or production, clear the package cache so nodes do not serve stale data. If you adopt the package, make the wrapper the only access path so tests and cache-clearing behavior stay consistent across the application.