- How do I install ooiill/bsw-bundle in a Laravel application?
- Install it with Composer using composer require ooiill/bsw-bundle from your project root. Because the package ships a Laravel service provider with auto-discovery, no manual registration in config/app.php is normally required on supported Laravel versions. After installation, publish the configuration and assets if you need to customize the defaults.
- Does ooiill/bsw-bundle support Laravel package auto-discovery?
- Yes. The bundle is described as offering Laravel integration with service provider auto-discovery, so Laravel registers the provider automatically once Composer has installed the package. If you are on an older Laravel version without discovery, you would add the provider to the providers array in config/app.php manually. Check the package README for the exact provider class name.
- How do I publish the BSW bundle configuration file?
- The package provides publishable configuration for environment-specific setup. Run php artisan vendor:publish and select the BSW bundle tag or provider to copy the config file into your application's config directory. Once published, you can set environment-driven values in your .env file and reference them from the config.
- How do I publish the assets that ship with this package?
- Asset publishing is one of the bundle's stated features, so the resources are copied into your public directory through Laravel's vendor:publish command. Run the command and choose the asset tag associated with the bundle. Afterwards the files live in your application and can be versioned or modified as needed.
- Which Laravel and PHP versions does ooiill/bsw-bundle support?
- The package targets Laravel applications and is installed as a standard Composer dependency, but the exact version constraints are declared in its composer.json. Check the require section on Packagist or in the repository before upgrading Laravel or PHP. Matching your application's framework version to those constraints avoids resolution conflicts.
- Can I extend the BSW bundle for custom workflows?
- Yes. The package is described as having an extensible structure for custom BSW workflows, so you can build on top of the provided services rather than editing vendor code. Keep your customizations in your own application classes or a separate package so Composer updates do not overwrite them. Published configuration also lets you adjust behavior per environment without forking.
- Is ooiill/bsw-bundle safe to use in production?
- The bundle emphasizes minimal setup, sensible defaults, and predictable integration, which are good signs for production use. Before deploying, publish and review the configuration, confirm the asset publishing step runs in your deployment pipeline, and pin the version in composer.lock. As with any package, review the repository's recent activity and issue tracker for your own risk assessment.
- How do I set environment-specific options for the BSW bundle?
- Publish the package config file first, then drive its values from environment variables rather than hardcoding them. That lets you keep different settings for local, staging, and production without changing code. Laravel's config caching works normally as long as you avoid calling env() outside config files.
- How do I test an application that uses this bundle?
- Because the provider is auto-discovered, it loads in Laravel's test environment the same way it does in production, so standard PHPUnit or Pest feature tests will exercise the bundle. Publish the config into your test setup or define the relevant environment variables in phpunit.xml. If you need isolation, you can mock the bundle's services through the container.
- What are the alternatives to ooiill/bsw-bundle?
- Alternatives depend on what BSW functionality you need: you can implement it directly in your application, extract it into your own private Composer package, or look for a more actively maintained package covering the same domain. The bundle's value is convenience, since it packages the services, configuration, and assets with auto-discovery already wired up. If you only need a small part of that, a hand-rolled service class may be simpler to maintain.