Skip to content

Settings syncronization with config/settings.php #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

eduardoarandah
Copy link
Contributor

Settings syncronization with config/settings.php

Command settings:sync helps you keep production settings in sync with
config/settings.php
It doesn't override "value" field

Package now publishes config/settings.php

Backwards compatiblity

What could go wrong?

If user upgrades to this version, then doesn't have any config/settings.php file and runs php artisan settings:sync it'll use dummy settings in the package, removing user settings in their database.

This is not a likely scenario of a cautious programmer running any command in production, but it'll be a good security check to have.
(I'm not sure how to check for config/settings.php in user code only)

------------------------------------------------

Command settings:sync helps you keep production settings in sync with
config/settings.php
It doesn't override "value" field

Package publishes config/settings.php
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant