Weave Code
App Bundle Laravel Package
gdbots/app-bundle
Gdbots App Bundle packages shared Symfony application infrastructure for Gdbots PHP projects: base controllers, reusable services, configuration defaults, and Twig helpers. It helps teams bootstrap and standardize apps with less boilerplate and consistent conventions.
gdbots/app-bundle is a Symfony bundle that provides the foundational plumbing for building GDBots applications. It standardizes application bootstrapping and service configuration so your app shares a consistent structure with the wider GDBots ecosystem.
- Provides a reusable base application kernel and bundle setup.
- Centralizes service and dependency-injection configuration.
- Integrates common GDBots application conventions and defaults.
- Simplifies environment-specific configuration for development and production.
Frequently asked questions about App Bundle
- Is gdbots/app-bundle a Laravel package or a Symfony bundle?
- gdbots/app-bundle is a Symfony bundle, not a Laravel package. It ships as a Symfony\Component\HttpKernel\Bundle\Bundle subclass with a DI extension and a Configuration tree, and it is registered through config/bundles.php plus YAML config. There is no Laravel ServiceProvider, no config/app.php entry point, and no Laravel-facing facade.
- Can I install gdbots/app-bundle in a Laravel application?
- You can technically add it with Composer, but it is not a clean fit for Laravel. The bundle assumes Symfony kernel conventions and pulls in the Gdbots platform, so you would end up mixing Symfony framework pieces into a Laravel app. The assessment recommends concept transfer instead: read its configuration and service-wiring ideas and reimplement only the relevant parts with Laravel service providers, the queue, and Illuminate\Contracts\Bus.
- How do I install and register gdbots/app-bundle in Symfony?
- In a Symfony project, install it with Composer and register the bundle in config/bundles.php, then configure it through YAML. The bundle supplies a DI extension and a Configuration tree, so its options are exposed through normal Symfony bundle configuration. There is no Laravel-style provider registration path.
- What Laravel version does gdbots/app-bundle support?
- There is no Laravel version support because this is a Symfony bundle, not a Laravel package. For Symfony, the key question is which Symfony major versions and PHP versions its composer.json allows and whether that intersects your runtime. Check the root composer.json constraints before planning any adoption.
- What does gdbots/app-bundle actually provide?
- It is a thin convention layer for Gdbots-based Symfony applications: base configuration, common service definitions, message-bus and envelope conventions, and environment defaults. Its value depends heavily on adopting the surrounding Gdbots libraries such as gdbots/pbj, gdbots/ncr, gdbots/messenger-*, and the Triniti platform. On a plain Symfony app by itself, it is likely to be only a small amount of configuration sugar.
- What are the risks of adopting gdbots/app-bundle?
- The main risk is ecosystem coupling: adopting this bundle means adopting the Gdbots platform, and each transitive gdbots/* package carries its own abandonment risk. External validation is very low at 3 stars and 0 dependents, and documentation is likely sparse, so budget time to read source. Version-range conflicts with symfony/framework-bundle, symfony/messenger, or your PHP minor version can also cause hard Composer resolution failures.
- How do I test gdbots/app-bundle before adopting it?
- Do a short spike rather than a full trial: inspect the root composer.json for required gdbots/* packages, Symfony and PHP constraints, and abandoned dependencies. Then check how many services the extension registers, whether the bundle assumes a specific kernel layout or env var set, and whether CI has test coverage. Also review release history for semver discipline, especially breaking changes on minor bumps.
- Is gdbots/app-bundle actively maintained?
- The 2026-01-16 release indicates active, recent development, so it is not a dead repository. However, 3 stars and 0 dependents suggest it is published for the vendor's own products rather than broad community use. Apache-2.0 licensing means you retain the fork option if you adopt it.
- What are alternatives to gdbots/app-bundle for Laravel?
- For Laravel, the realistic alternative is not another drop-in package but native implementation: use Laravel service providers, the queue, and Illuminate\Contracts\Bus to reproduce the relevant conventions. If you need the full Gdbots stack, run it in a separate Symfony service rather than forcing Symfony bundles into Laravel. Adopting the bundle alone on a plain Symfony app is also usually not worth it unless you are already in the Gdbots ecosystem.
- Can I use gdbots/app-bundle standalone or in a greenfield service?
- Standalone use is questionable because the bundle is designed to wire a Symfony kernel to the Gdbots stack and likely assumes specific conventions. A greenfield Symfony service that adopts Gdbots in isolation is the cleaner path, communicating with your Laravel app over a service boundary. Resolve in a spike whether the bundle assumes a particular kernel layout, directory structure, or environment variable set.
Weaver
How can I help you explore Laravel packages today?