The latest articles on DEV Community by Mohamed (@m7mdsa3ed_). https://dev.to/m7mdsa3ed_ https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F470637%2Fabd16b63-e6eb-41a0-a1d0-ff7509d69bb5.png https://dev.to/m7mdsa3ed_ en Mohamed Sun, 07 Nov 2021 10:43:19 +0000 https://dev.to/m7mdsa3ed_/laravel-is-it-okay-to-change-the-config-in-runtime-3bmk https://dev.to/m7mdsa3ed_/laravel-is-it-okay-to-change-the-config-in-runtime-3bmk <p>I was working on implementing settings for emails, taxes, SMS providers so the client can change the credentials by themselves and switch between some providers. </p> <p>That credentials and active providers are stored in the database, and I get 'em in the AppServiceProvider and overrider the config with 'em</p> <p>But I had an issue with Queue Jobs</p> <blockquote> <p>Since queue workers are long-lived processes, they will not notice changes to your code without being restarted</p> </blockquote> <p>So I was in front of 2 solutions </p> <ul> <li>Restart the worker after updating DB </li> <li>Change how some integrated services like "Mail" get the config and replace 'em from database</li> </ul> <p>I choose the 2nd solution since it's challenging 🙂</p> <h2> But it okay to do so "Change the config in runtime"? I just dunno, maybe I'll have some issue like this in the future. </h2> laravel