Weave Code
Configuration Laravel Package
elcodi/configuration
elcodi/configuration is a PHP component for managing configurable settings in Elcodi applications. It provides configuration entities, repositories, and services to persist and retrieve key-value options, helping e-commerce stores handle dynamic settings cleanly.
[READ-ONLY] Subtree split of the Elcodi Configuration component
Frequently asked questions about Configuration
- Is elcodi/configuration compatible with Laravel?
- It is not Laravel-native. It is a Symfony-oriented component from the Elcodi e-commerce framework and assumes Symfony's dependency injection container and Doctrine ORM. Laravel uses Eloquent and its own container, so there is no service provider or bridge. Treat it as a legacy Symfony artifact, not a drop-in Laravel package.
- How do I install elcodi/configuration?
- You would normally add it with Composer, but it is a read-only subtree split of the Elcodi monorepo. Its legacy Symfony and Doctrine constraints may fail to resolve on modern PHP stacks, so run a Composer dry-run first. There is no Laravel package discovery or service provider, so installation alone will not wire it into a Laravel app.
- What PHP and Symfony versions does elcodi/configuration support?
- The component originates from the PHP 7.x, Symfony 2/3, and Doctrine 2.x era, all now end-of-life. The repository provides no compatibility guarantees for PHP 8.2 or 8.3 or for current Symfony and Doctrine releases. Check the parent Elcodi monorepo's Composer constraints before assuming support.
- Can I use elcodi/configuration with Eloquent instead of Doctrine?
- Not directly. The component's entities, repositories, and managers are built around Doctrine ORM and Symfony conventions. To use Eloquent you would need to reimplement the Configuration and ConfigurationGroup schema as Laravel models. At that point you are lifting the data shape, not integrating the package.
- Is elcodi/configuration actively maintained?
- No meaningful maintenance signal exists. It is a read-only subtree split with zero stars and zero dependents, and upstream Elcodi has been dormant for years. Issues and pull requests belong to the parent monorepo, not this repository. Adopting it means owning fixes and security patches yourself.
- What are the best Laravel alternatives to elcodi/configuration?
- For Laravel settings, consider spatie/laravel-settings, a custom settings table with typed casts, or Laravel's built-in config repository for static configuration. These options fit Eloquent, the Laravel container, and modern PHP versions. They also avoid inheriting abandoned Symfony and Doctrine dependencies.
- How does elcodi/configuration store settings?
- It provides Doctrine-backed configuration entities, typically Configuration and ConfigurationGroup, plus repositories and services. Values are persisted as key-value options, often grouped for store-level settings such as currency, locale, shop name, or feature flags. Retrieval and persistence go through the component's managers rather than Laravel's config helper.
- Can I migrate elcodi/configuration data to a Laravel app?
- Yes, but migrate the data, not the package. Extract the Configuration and ConfigurationGroup tables from the legacy Elcodi database and map them to Eloquent models or a Laravel settings package. This preserves historical rows while discarding the unusable Symfony and Doctrine wiring. It is the lowest-risk path for a greenfield Laravel build.
- Is elcodi/configuration safe to use in production?
- The technical risk is high. The package has no active maintainer, no patching path, and inherits legacy Symfony, Doctrine, and PDO dependencies that may carry known CVEs. It also lacks compatibility guarantees for current PHP versions. For a new production build, a maintained Laravel-native alternative is safer.
- Does elcodi/configuration support grouped key-value configuration?
- Yes, its domain model typically includes Configuration and ConfigurationGroup entities for grouped key-value settings. That grouping is useful for store-level options like locale, currency, and feature flags. However, the grouping logic is tied to Doctrine repositories and Elcodi managers, so it does not plug into Laravel's config system.
Weaver
How can I help you explore Laravel packages today?