[5.x] Suggestion : Modify storage
variable in default config file
#1444
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During the Laravel 11 update, I encountered a minor issue. Since I have a dedicated database for data from Pulse or Telescope, I needed to redirect connections to this database when loading the Pulse and Telescope dashboards.
For Pulse, it's straightforward to implement this using an environment variable called 'PULSE_DB_CONNECTION.' However, Telescope has a similar configuration with the environment variable 'DB_CONNECTION,' which is the
database.default
connection env variable.A workaround could be to rewrite this in a dedicated config file, of course. However, I still thought it would be beneficial to suggest this pull request due to the current behavior of Pulse.
Pulse's default
config
filestorage
value :Telescope's default
config
filedriver
andstorage
values :P.S.: The description has been copied and pasted from the Pulse description and used for Telescope.