This repository has been archived by the owner on Aug 2, 2024. It is now read-only.
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.
[FEATURE] Allow use in production
Issue or feature explanation
Providing the option to access Prequel in production will allow it to be used in system administrator dashboards for inexpensive DB operations. Setting it behind a warning and defaulting it to false will discourage its use for those who don't know exactly what they are doing.
Proposed solution/change
An additional boolean config setting (default: false) which can be enabled from .env was added to config/prequel.php. This variable is then checked in the Authorised middleware, allowing the configuration check to return true for enabled when the app environment is production and the production_enabled flag is enabled.
Love this package by the way, it's so much better than phpMyAdmin.