Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support configuration #5

Open
amenk opened this issue Jan 21, 2013 · 2 comments
Open

Support configuration #5

amenk opened this issue Jan 21, 2013 · 2 comments

Comments

@amenk
Copy link
Contributor

amenk commented Jan 21, 2013

Show we also support core_config_data ?

But it would be handy to have exclude filters. Scenario: Config is tested on a staging system with special test settings that should not be transfered to the live system.
@airbone42
Copy link
Member

I would suggest having a configurable blacklist for data which should not be stored on the filesystem

@avstudnitz
Copy link
Contributor

@vfranz wanted to address that - we already thought about that. As far as I know, his idea was to have a seperate form to confirm saving of changed attribute, but I like the blacklist idea too.

@amenk amenk mentioned this issue Mar 27, 2013
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@avstudnitz @amenk @airbone42