Weave Code
Static Data Bundle Laravel Package
forci/static-data-bundle
Forci StaticDataBundle helps Symfony applications manage static and reference data through reusable entities, configurable data sets, and simple CRUD workflows. Keep lookup values centralized and maintainable without duplicating code.
Static Data Bundle
Frequently asked questions about Static Data Bundle
- Is forci/static-data-bundle a Laravel package?
- No. It is a Symfony bundle built around a Bundle class registered in config/bundles.php, a DependencyInjection Configuration tree, Doctrine entity mappings, and console commands. Laravel provides none of those layers, so it will not install or boot as a Laravel package. Treat any Laravel usage as a rewrite, not an integration.
- How do I install forci/static-data-bundle in a Laravel application?
- There is no supported path. A credible port would need a custom service provider replacing the DI extension, a hand-translated config file, migrations plus Eloquent models replacing the Doctrine mappings, and Artisan equivalents of every console command. By the time that mapping is complete, essentially none of the original package remains. Fund it as a short spike with a written deliverable, not an integration ticket.
- What does forci/static-data-bundle actually do?
- It keeps static reference data such as countries, statuses, categories, and currency lists defined as versioned configuration instead of scattered database rows. That data is exposed through a service API wired into the Symfony container and synced into Doctrine-backed tables. The stated goal is centralizing lookup values so they stay in version control and do not drift between environments.
- Can I use forci/static-data-bundle for country, status, or category lookups?
- Conceptually yes, enum-like lookups are exactly the use case it targets. In a Laravel stack you would be rebuilding the sync and persistence layers yourself, which is most of the work. Most Laravel teams get further with config files, seeders, enum casts, or a small cached lookup table with a deterministic refresh job.
- Does forci/static-data-bundle require a database?
- Yes, and this is a material correction to the marketing copy. The implementation surface implies Doctrine-backed persistence for the reference rows, so a database is part of the integration footprint. That makes it a larger dependency than a plain array or config provider, despite the static data framing.
- What PHP, Symfony, and Doctrine versions does forci/static-data-bundle support?
- The declared constraints are not documented in the available material, so inspect composer.json directly before anything approaches production. Laravel ships selected Symfony components and Illuminate's own ORM, not Doctrine ORM, so any Doctrine version floor or transitive constraint is a genuine conflict risk. Confirm the version matrix resolves cleanly against your target Laravel and PHP versions.
- What are the sync command semantics in forci/static-data-bundle?
- Unknown from the available documentation. It is not established whether the sync command upserts only, hard-deletes rows removed upstream, or wraps the whole operation in a transaction, nor whether re-running it is safely idempotent. This is the riskiest unknown, because a reference-data sync that mishandles deletions, renames, or repeat runs can corrupt production lookup tables. Read the command source end to end before trusting it.
- Is forci/static-data-bundle actively maintained and safe for production?
- There is no visible evidence of maintenance or external validation. Zero stars, zero dependents, no surfaced README, and no issue history mean no usage corpus and no downstream bug reports. Data freshness is also unverified, and reference data decays silently, so a stale snapshot fails without an obvious outage. Treat it as high risk until proven otherwise.
- What license is forci/static-data-bundle released under?
- Repository metadata reports NOASSERTION, meaning no clear grant of rights is established. Embedded data compilations can also carry upstream terms that are independent of the code license. Legal must resolve both the code and the data provenance before anything is vendored or redistributed commercially.
- What are the best alternatives to forci/static-data-bundle for a Laravel app?
- Keep reference data in version-controlled PHP config or JSON files, seed it through idempotent migrations or seeders, and expose it behind a small cached repository service. For enum-like values, native PHP enums plus casts cover most cases without any package. If you only want the bundled data, consider extracting it as a plain JSON artifact and dropping the Symfony bundle entirely.
Weaver
How can I help you explore Laravel packages today?