Weave Code
Studio Addons Laravel Package
botman/studio-addons
Official add-ons for BotMan Studio that extend Laravel-based chatbot projects with extra integrations, helpers, and configuration to speed up development.
BotMan Studio addons
Frequently asked questions about Studio Addons
- What is botman/studio-addons used for?
- botman/studio-addons provides official add-ons for BotMan Studio, extending Laravel-based chatbot projects with extra integrations, helpers, and configuration. It is meant to speed up development inside an existing BotMan Studio application rather than act as a standalone chatbot framework. The package is a process-orchestration adapter around an external binary or CLI invoked with Symfony Process.
- How do I install botman/studio-addons in a Laravel app?
- Install it with Composer, publish the package configuration, and wire in its service provider. The critical step is ensuring the underlying external binary is present in the container or runtime and executable by the PHP-FPM or queue worker user. Validate one end-to-end invocation in a containerised environment before rolling it out broadly.
- Which Laravel versions does botman/studio-addons support?
- Version 1.6.1 supports Laravel 7 and 8 and uses Symfony's Process component. Laravel 9 and 10 support is not indicated in the provided assessment, so verify the package's Composer constraints and roadmap before upgrading. Because it depends on Laravel framework internals, expect to review it at each framework upgrade.
- Does botman/studio-addons require an external binary?
- Yes. The package wraps an external binary or CLI through Symfony Process rather than doing all work in-process. That binary must be installed in every environment, including local, CI, staging, production, and ephemeral build containers. Bake it into your Docker image rather than installing it as a post-deploy step.
- How do I configure botman/studio-addons after installation?
- After Composer install, publish the package configuration and wire in its service provider. The main configuration concern is the external binary: confirm its path, supported version, and executable permissions for the PHP-FPM or queue worker user. Check the package documentation for the exact config keys and supported binary range.
- Is botman/studio-addons production-ready?
- The technical risk is medium. The 1.6.1 Process fix addresses a compatibility break that would have caused runtime exceptions under Laravel 7 and 8, which meaningfully de-risks adoption. Residual risk remains because the package depends on an external tool you do not control, so validate it with a single non-critical use case first.
- How do I test botman/studio-addons in CI?
- Make the external binary available in your CI image at the correct version and ensure it is executable by the CI user. Run at least one end-to-end invocation in a containerised environment before broad adoption. The Symfony Process layer can be tested around your integration boundaries, but the binary itself is an OS-level dependency.
- What are the main risks of using botman/studio-addons?
- The primary risks are subprocess overhead, OS-level dependencies, and version drift between the package, the external binary, and Laravel's Symfony components. The package depends on Laravel's framework version, so it will be a recurring item in framework upgrades. Maintainer risk is not clear from the release notes, so check commit cadence, open issues, and the gap before 1.6.1.
- Is botman/studio-addons compatible with Laravel 9 or Laravel 10?
- Laravel 9 and 10 compatibility is not indicated in the provided assessment; version 1.6.1 supports Laravel 7 and 8. Confirm the package's Composer constraints and roadmap before planning an upgrade. Without an explicit release, assume you may be pinned to Laravel 8 within a release cycle or two.
- What alternatives to botman/studio-addons should I consider?
- If you only need process execution, use Symfony Process directly or maintain a small wrapper. If you need the official BotMan Studio extras, this package is the intended path. If a homegrown exec or shell_exec wrapper already exists, replace it feature-by-feature behind the package's API so behaviour can be diffed per call site.
Weaver
How can I help you explore Laravel packages today?