Weave Code
Gpp App Bundle Laravel Package
goldenplanetdk/gpp-app-bundle
gpp-app-bundle is a PHP application bundle from Golden Planet that packages shared setup and integration code for GPP projects. It offers a reusable foundation for standardizing common app functionality, configuration, and service wiring across applications, reducing duplicated boilerplate.
goldenplanetdk/gpp-app-bundle is a PHP application bundle that packages shared application infrastructure for Golden Planet projects. It offers a consistent foundation for bootstrapping, configuration, and common services, reducing boilerplate and keeping applications aligned.
- Shared configuration for consistent project setup
- Reusable application services for common concerns
- Composer-ready integration with modern PHP workflows
- Extensible structure for project-specific customization
- Golden Planet DK maintained for internal and partner projects
Frequently asked questions about Gpp App Bundle
- Is goldenplanetdk/gpp-app-bundle a Laravel package?
- No. It is a Symfony bundle, not a Laravel package. Laravel has no concept of bundles: there is no Bundle class registration, no DependencyInjection Extension, no compiler passes, and no automatic loading of Resources/config/services.yaml. A bundle's entry point is the Symfony kernel and bundles.php, which Laravel never invokes.
- Can I just run composer require goldenplanetdk/gpp-app-bundle in a Laravel app?
- Composer may install the code, but nothing will be wired up. Laravel will not register the bundle, load its configuration tree, routes, Twig paths, or Doctrine mappings. The evaluation recommends treating any assumption that it drops into a Laravel app as false before estimating work.
- Which Symfony and PHP versions does gpp-app-bundle support?
- That is not documented in the public package information and is one of the first questions to raise with the vendor. Inspect composer.json directly to see whether PHP and Symfony constraints are pinned, for example ^6.4 or ^7.x, or left open. An open constraint increases the risk of silent breakage on framework upgrades.
- How do I integrate a Symfony bundle into a Laravel application?
- There is no supported bridge; packages like laravel-symfony-bundle exist but are unmaintained and break on major-version bumps. The pragmatic path is extraction rather than installation: read the source, list every public class, and mark each as framework-agnostic, Symfony-component-based, or Symfony-framework-coupled. Only the reusable subset can be forked into a Laravel package with a ServiceProvider, config publishing, and contract bindings.
- What does GPPAppBundle actually contain?
- The overview describes shared app scaffolding and common services for the Golden Planet Platform, with opinionated defaults for bootstrapping projects. The public documentation does not enumerate the API surface or the dependency footprint. A source read is required to determine what is plain PHP versus what is DI wiring, config trees, routes, and Doctrine mappings.
- Does gpp-app-bundle ship Doctrine entities or database migrations?
- This is unconfirmed and is the single biggest integration hazard to resolve before adoption. If the bundle owns entities or migrations, it also owns database schema, which forces migration work and long-term coupling to its data model. Check for Doctrine ORM and DBAL dependencies in composer.json and inspect any shipped mappings before planning integration.
- Is goldenplanetdk/gpp-app-bundle actively maintained and production ready?
- The evidence points to an internal extraction from Golden Planet's own application rather than a supported distribution. It has zero stars, zero dependents, single-vendor ownership, no public documentation, and no community to absorb breakage. A 2025-12-03 release date suggests activity but not that external consumers are a design goal, so the evaluation rates technical risk as high.
- What are the alternatives to using gpp-app-bundle in a Laravel project?
- There are three viable paths, all requiring a spike. Port selected services into a Laravel package with a ServiceProvider, which works only if coupling to Symfony's container and Doctrine is shallow. Run a sidecar Symfony service over HTTP or a queue, which carries high operational cost. Or abandon and reimplement, which is often correct for thin bundles.
- How should I test or spike an integration with gpp-app-bundle?
- Fund a 3 to 5 day spike to read the source and produce a class-by-class coupling inventory before adding it to any roadmap. Inspect composer.json for supported PHP and Symfony ranges and Resources/config for the real wiring and configuration tree. For the reusable subset, vendor a fork into packages/gpp-app with a Laravel ServiceProvider and wrap it in contract tests asserting behaviour parity where possible.
- What license does gpp-app-bundle use and is commercial support available?
- The package is MIT licensed, which is clean and removes legal friction. The open question is whether there is any commercial support relationship with Golden Planet or whether this is best-effort open source. Ask the owning team directly, since undocumented API surface plus no support agreement is a significant long-term maintenance risk.
Weaver
How can I help you explore Laravel packages today?