You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been looking at this package to see if it can replace our homegrown service but we also have the same limitation, our config data would also come from the database (clients can change prefixes and patterns). Don't see a built-in way to dynamically change the configuration.
@yashiroiori@deviarte
Thanks a lot for the feedback and for checking out the package! 🙌
You’re right — at the moment, the configuration is loaded from the config file and doesn’t support dynamic values from the database out of the box.
However, it’s definitely possible to extend this in your own project — for example, by loading your config data at runtime and updating it using Config::set() or within a custom service provider.
That said, adding native support for database-driven configuration is a great idea and something I’d love to explore in future releases.
All contributions are very welcome — so if you’d like to help implement this feature or propose an approach, feel free to open a PR or start a discussion.
Activity
deviarte commentedon Oct 8, 2025
We have been looking at this package to see if it can replace our homegrown service but we also have the same limitation, our config data would also come from the database (clients can change prefixes and patterns). Don't see a built-in way to dynamically change the configuration.
EG-Mohamed commentedon Oct 9, 2025
@yashiroiori @deviarte
Thanks a lot for the feedback and for checking out the package! 🙌
You’re right — at the moment, the configuration is loaded from the config file and doesn’t support dynamic values from the database out of the box.
However, it’s definitely possible to extend this in your own project — for example, by loading your config data at runtime and updating it using Config::set() or within a custom service provider.
That said, adding native support for database-driven configuration is a great idea and something I’d love to explore in future releases.
All contributions are very welcome — so if you’d like to help implement this feature or propose an approach, feel free to open a PR or start a discussion.
Thanks again for your input and support! 🚀