- What is addgod/laravel-mandrill-template used for?
- It is a Laravel integration for Mandrill's template system, intended to make sending transactional emails through Mandrill templates easier. The package provides a simple API for incorporating Mandrill templates into Laravel mail flows. It fits Laravel applications that want template-driven transactional email rather than hand-building every message body.
- How do I install addgod/laravel-mandrill-template in Laravel?
- Install it with Composer using composer require addgod/laravel-mandrill-template. Then follow the package README for service provider registration, configuration publishing, and Mandrill API key setup. The release is described as additive, so existing mail flows should usually remain unchanged after installation.
- Does this package support runtime Mandrill API key overrides?
- Yes, the TPM assessment describes a runtime API-key override capability added in a patch release. This is useful for per-tenant, per-request, or per-job credentials without redeploying configuration. You should confirm the exact function signature, return behavior, and reset semantics in the package source or README before relying on it.
- Is the runtime API key override safe with Laravel Octane and queue workers?
- It can be safe only if the override is scoped to a single request or job and reliably reset afterward. In Octane, queue consumers, and long-running workers, mutating global config without clear reset behavior can leak one tenant's key into another execution. Validate behavior in your actual runtime model and wrap the override in a thin application service that enforces scoping.
- Which Laravel and PHP versions does this package support?
- The repository README and composer.json are the authoritative source for minimum PHP and Laravel versions. The TPM assessment notes that the runtime override arrived as a patch release, so you should confirm compatibility before upgrading. Do not assume Octane, Swoole, RoadRunner, or specific queue-driver compatibility without testing.
- How do I configure the Mandrill API key?
- Typically you provide the Mandrill API key through environment-driven package configuration, then use the runtime override only when you need dynamic credentials. The README is the authoritative source for the exact config file and variable names. Avoid logging the key or exposing it through debug output and exception traces.
- Can I use different Mandrill API keys for each tenant or customer?
- Yes, that is the main use case for the runtime API-key override. You must scope each override to the current request or job and restore the default key afterward, especially in multi-tenant or high-concurrency applications. A thin wrapper around the override function helps prevent cross-tenant credential contamination.
- Does it work with Laravel config caching?
- Static package configuration should remain compatible with Laravel's config:cache workflow because cached config is loaded normally. Runtime overrides happen outside the cached configuration, but the TPM assessment flags potential conflicts with config:cache and environment-based configuration as something to validate. Test both cached and uncached deployments before rolling out.
- How should I test runtime API key overrides in my application?
- Add targeted tests for default API key fallback, runtime override, and explicit reset behavior. If you use queues, Octane, or long-running workers, include tests that simulate consecutive jobs with different credentials. A thin application wrapper around the override function makes scoping easier to test and enforce.
- Is addgod/laravel-mandrill-template maintained, and what are the alternatives?
- Check the repository's recent commits, releases, and issue activity to judge maintenance; the TPM assessment expects low maintenance burden if the package remains active. Alternatives include direct Mandrill API calls, other community Mandrill mail packages, or your existing Laravel mail setup for static credentials. Choose this package when Mandrill template integration in Laravel mail flows is the priority. Pin the version and review patch notes before upgrading.