Weave Code
Mindbaz Bundle Laravel Package
kozikaza/mindbaz-bundle
A Symfony bundle that integrates Mindbaz email marketing with your PHP application. It provides configuration and service wrappers for connecting to Mindbaz APIs, helping manage contacts, campaigns, and transactional email workflows from within Symfony.
At a glance
Frequently asked questions about Mindbaz Bundle
- Is kozikaza/mindbaz-bundle compatible with Laravel?
- It is a Symfony bundle, not a Laravel package. It relies on Symfony's dependency injection container, config tree, and bundle registration conventions; there is no Laravel ServiceProvider, facade, publishable config, or package auto-discovery. You cannot Composer require it and use it idiomatically in Laravel without an adapter layer or a fork.
- Can I install kozikaza/mindbaz-bundle with Composer in a Laravel app?
- You can technically require it if constraints resolve, but it will not register in Laravel. Expect dependency conflicts because it targets Symfony components and likely older PHP/Symfony constraints; Composer resolution against Laravel 10/11 on PHP 8.2+ should be assumed to fail until proven otherwise. Installation alone does not provide usable Laravel integration.
- How do I configure Mindbaz credentials and endpoints?
- In Symfony the bundle exposes configuration through its config tree and service definitions. There is no publishable Laravel config file; in an adapter or fork you would map credentials and endpoints into your own config repository. Keep credentials out of version control and load them from environment variables.
- How do I send a transactional email with this bundle?
- The bundle provides service wrappers around Mindbaz REST endpoints for transactional and marketing email workflows. In Symfony you would inject the service and call its send method; in Laravel you would need to bind the underlying transport into the container first. Verify the current Mindbaz API contract and authentication model, because the package predates recent API changes.
- Does it support subscriber and list management?
- Yes, the described scope includes managing subscribers and lists through Mindbaz API wrappers. The Mindbaz domain surface—subscriber sync, list management, and campaign triggers—is relatively small. For Laravel, a thin hand-rolled client against the current Mindbaz REST API may be cheaper than adapting Symfony glue.
- Which Laravel and PHP versions does it support?
- It does not target Laravel versions at all; it is a Symfony bundle. PHP and Symfony constraints may be old and end-of-life, and the v1.1.0 bugfix release does not prove they moved. Run Composer outdated and inspect composer.json on the tag before assuming PHP 8.2+ or Laravel 10/11 support.
- Is kozikaza/mindbaz-bundle actively maintained?
- Release cadence is mixed. A prior assessment saw a 2017 last release, but v1.1.0, labeled Fix #7 and #8, shows someone is still tagging. The release notes are thin with no changelog and no linked pull requests, so treat active maintenance as unproven; bus factor remains one maintainer.
- What do issues #7 and #8 fix in v1.1.0?
- The provided release notes only say Fix #7 and #8 with no further detail. It is unclear whether they are bugfixes, security fixes, or dependency bumps. Review the tag diff, especially composer.json, services.yml, and the HTTP transport, before relying on the release.
- Is it safe for production email marketing and GDPR?
- Email marketing data is PII, so a thinly maintained library handling subscriber records is a compliance liability if it logs payloads or lacks consent-state handling. Low activity does not remediate that risk. The MIT license is clean, but production use should include payload redaction, consent tracking, and a security review.
- Are there alternatives or should I fork it for Laravel?
- Options are to fork it under the MIT license, extract the Mindbaz HTTP transport and DTOs into a framework-agnostic class bound into Laravel's container, or hand-roll a thin client against the current Mindbaz REST API. Extraction cost depends on hard Symfony dependencies such as ParameterBag, ConfigDefinition, or the event system. If it wraps an official Mindbaz SDK, depending on that SDK directly may be the best path.
Weaver
How can I help you explore Laravel packages today?